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

Text File | 1993-12-31 | 219.1 KB | 5,742 lines

Fri,  1 May 92 04:30:02 PDT
From: Packet-Radio Mailing List and Newsgroup <[e-mail]>
Errors-To: [e-mail]
Reply-To: [e-mail]
Precedence: Bulk
Subject: Packet-Radio Digest V92 #116
To: packet-radio


Packet-Radio Digest         Fri,  1 May 92       Volume 92 : Issue 116

Today's Topics:
         3th Week of Computing Systems Engineering...
       Connecting the PAKRATT 232 MBX to the TS 690S. (2 msgs)
            K9NG data recovery mod
                  NOS, etc.
         PK232 with G3RUH ? Anyone? (2 msgs)
                 police MDT's
             Undeliverable Mail (2 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: 30 Apr 1992 07:29:36 -0700
From: [e-mail]
Subject: 3th Week of Computing Systems Engineering...
To: [e-mail]

Hi,

the "....@Iteso...." may be an unreacable address!

Mitch
KB0GNY
:)

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

Date: 30 Apr 1992 04:54:26 -0700
From: [e-mail]
Subject: Connecting the PAKRATT 232 MBX to the TS 690S.
To: [e-mail]

I have a question with regards to linking the 232mbx to the 690s using
the ACC2 port. I have had no problems with the receive part of the
connectors BUT have had no luck in being able to get the 232 to
activate the transmit (PTT)line on the 690. The loop test with the 232 indicates
that all is fine with the audio output of the 232. In the manual the red or
number 5 wire is to be attched to pin 13 of the ACC2. AeA reps have
indicated that it can be attached to pin 9 instead. I've tried both and
have been unable to get the 2323 to activate the transmit action of the
690s even with the mic gain full open, and the AFSK output of the 232
turned full open. All other settings indicated in the manual for the rig
were followed. Yet NO power output or ALC action  was displayed on the front
panel when I throw the 232 into the transmit mode ( using  "K" when in
 the dumb terminal which is in calibrate " CAL" mode).

Is it necessary to internally ajust the sensitivity of the AC2, am I missing a
switch in the 690s that must be turned on ????  etc?

I would appreciate any comments to be sent to me direct at  [e-mail].

Thankyou for your help in this matter.

David Seeler
[e-mail]

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

Date: Thu, 30 Apr 1992 12:51:20 GMT
From: pa.dec.com!nntpd2.cxo.dec.com!nntpd.lkg.dec.com!asia.enet.dec.com![e-mail]
Subject: Connecting the PAKRATT 232 MBX to the TS 690S.
To: [e-mail]

>>turned full open. All other settings indicated in the manual for the rig
>>were followed. Yet NO power output or ALC action  was displayed on the front
>>panel when I throw the 232 into the transmit mode ( using  "K" when in
>> the dumb terminal which is in calibrate " CAL" mode).

This may be a silly question but,


Is the parameter XMITOK set to 1 on the PK232?

--
--------------------------------------------------------------------------
Jeff McLeman, N1IPN        email:  [e-mail]
               UUCP: ...decwrl!asia.enet.dec.com!mcleman
               packet: n1ipn @ wa1phy.ma.usa.na

 Views expressed here are mine, exclusively. They are not in any way
 connected to my employer.

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

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

Date: 30 Apr 92 15:33:43 GMT
From: idacrd![e-mail]
Subject: K9NG data recovery mod
To: [e-mail]



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

Date: Thu, 30 Apr 1992 23:01:39 GMT
From: usc!sol.ctr.columbia.edu!bronze!newshost.cs.rose-hulman.edu![e-mail]
Subject: NOS, etc.
To: [e-mail]

I don't want to sound like too much of a neophyte, but...
before I came to college (5 years ago) I was quite active on packet
in the Chicago area.  I also ran KA9Q NET.EXE and I really liked it.
I checked back there and I guess my old address is still valid, and
I'd like to run TCP/IP again.  I guess now there will be more than
just 4-5 of us!  Anyway, I guess now its called NOS, and I'd like to
know the latest and greatest version of this for the IBM PC and where
to get it from.  I'm graduating and leaving May 23rd (goodbye Internet,
waaaaah!) and, being cheap, would like to know:  (1) what to get..
(2) a good FTP site to grab it from...

Thanks in advance.

Fred M. Spinner, KA9VAW
President, Rose-Tech Radio Club (W9NAA)
Rose-Hulman Institute of Technology.

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

Date: Thu, 30 Apr 1992 11:22:47 GMT
From: mcsun!news.funet.fi!uwasa.fi![e-mail]
Subject: PK232 with G3RUH ? Anyone?
To: [e-mail]

Has anyone used PK232 with G3RUH 9600 baud modem? I would be interested
to get info about the modifications for PK232 to get this beast working
with 9600 baud.

--
Markus Lamminmaki OH6LSA                Email: [e-mail]

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

Date: 30 Apr 92 15:56:25 GMT
From: idacrd![e-mail]
Subject: PK232 with G3RUH ? Anyone?
To: [e-mail]



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

Date: 1 May 92 01:41:58 GMT
From: swrinde!zaphod.mps.ohio-state.edu!moe.ksu.ksu.edu!hobbes.physics.uiowa.edu!iowasp.physics.uiowa.edu![e-mail]
Subject: police MDT's
To: [e-mail]

Does anybody know the actual data protocol for police MDT's? The police have
quit using their radios in town here and started installing MDT's in their
cars about 9 months ago. What frequencies do they use?
Thanks
John Kirby


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

Date: 30 Apr 1992 08:39:44 -0700
From: [e-mail]
Subject: Undeliverable Mail
To: [e-mail]

Unknown Microsoft mail form. Approximate representation follows.

Message: 3th Week of Computing Systems Engineering...
Sent: Thu, Apr 30, 1992 5:29 AM
To: HaeferJRichard
On Server: Server #72202177
Date: Thu, Apr 30, 1992 8:37 AM
Reason: Could not be delivered because the destination Microsoft Mail server
could not be found.

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

Date: 30 Apr 1992 09:15:10 -0700
From: [e-mail]
Subject: Undeliverable Mail
To: [e-mail]

Unknown Microsoft mail form. Approximate representation follows.

Message: 3th Week of Computing Systems Engineering...
Sent: Thu, Apr 30, 1992 5:54 AM
To: HaeferJRichard
On Server: Server #72202177
Date: Thu, Apr 30, 1992 9:07 AM
Reason: Could not be delivered because the destination Microsoft Mail server
could not be found.

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

Date: (null)
From: (null)
Both Paccomm and TAPR have little add ons that give a true TNC-2
style disconnect header to which the G3RUH (or NB-96 from Paccomm)
will plug directly.

Bob

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

Date: (null)
From: (null)
Great job Brian.  This falsing in the new state machine can only mean
that they have the gain on the equivalent DPLL the state machine is
trying to emulate unacceptably high.  It will result in quicker
acquisition but yield unacceptable jitter IF this is the case.  Who
did the new ROM?  I will make the mods to my two K9NG's and give
some feedback.

Bob

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

End of Packet-Radio Digest V92 #116
******************************
Date: Sat,  2 May 92 04:30:02 PDT
From: Packet-Radio Mailing List and Newsgroup <[e-mail]>
Errors-To: [e-mail]
Reply-To: [e-mail]
Precedence: Bulk
Subject: Packet-Radio Digest V92 #117
To: packet-radio


Packet-Radio Digest         Sat,  2 May 92       Volume 92 : Issue 117

Today's Topics:
              KA9Q's NOS and PPP
          Looking for NET/Mac HF PK-232 User
            PI boards and WNOS3B1

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 May 1992 11:48:34 -0500
From: ucselx!sol.ctr.columbia.edu!zaphod.mps.ohio-state.edu!cs.utexas.edu![e-mail]
Subject: KA9Q's NOS and PPP
To: [e-mail]

Hello !
Which versions on NOS include a PPP support ? Where can I get it ?

mni 73,
Claude Frantz (DJ0OT)

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

Date: 1 May 92 17:03:42 GMT
From: ucselx!sol.ctr.columbia.edu!usc!cs.utexas.edu!ut-emx!shrike![e-mail]
Subject: Looking for NET/Mac HF PK-232 User
To: [e-mail]

    - Is a Macintosh User
    - Running NET/Mac
    - thru a PK-232
    - On HF

I have a unique problem and would like to see if someone else has
solved the problem.

The problem is getting the PK-232 to accept a command from the
Console (or Autoexec.net file) to convert from VHF to HF.

Yes, I have tried 'param ax0 vhf OFF and hbaud 300'

The commands do not work.


Dick, KD5VU
[e-mail]
KD5VU @ N5LJF.#AUS.TX.USA.NA

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

Date: 2 May 92 02:00:34 GMT
From: mcdhup!viper![e-mail]
Subject: PI boards and WNOS3B1
To: [e-mail]

Hello group.

I have a few questions about WNOS that I hope someone can answer
for me.

(1) Does the attach scc in WNOS3B1 support the PI board? If so, do
both channels work?

(2) I notice that WNOS3B1 sees extended memory and reports it when
the memory status command is invoked. Does WNOS3B1 use the extended
memory? If so, for what?

(3) Is there a copy of WNOS4 at any anonymous FTP sites in the USA?


Thanks in advance.

Please reply to viper!kc2ky

73 from Neil Heft, KC2KY.

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

End of Packet-Radio Digest V92 #117
******************************
Date: Sun,  3 May 92 04:30:01 PDT
From: Packet-Radio Mailing List and Newsgroup <[e-mail]>
Errors-To: [e-mail]
Reply-To: [e-mail]
Precedence: Bulk
Subject: Packet-Radio Digest V92 #118
To: packet-radio


Packet-Radio Digest         Sun,  3 May 92       Volume 92 : Issue 118

Today's Topics:
ARRL's "Business Rule" proposal - automatic retransmission prohibited?
            KA9Q for the Hp 48sx??
                 police MDT's
               WNOS-4 and the PI card..

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: 2 May 1992 22:35:31 -0700
From: [e-mail]
Subject: ARRL's "Business Rule" proposal - automatic retransmission prohibited?
To: [e-mail]

AL N1AL replies to a previous posting, which in the name of brevity is
not included with:

>If you send packet through a voice repeater (or any other repeater that
>does not decode the packet and then reconstruct it before transmission),
>then I believe it would qualify as a "repeater" by FCC's definition.

Al, then I would assume by this that you would consider a "normal" (sic)
packet node/digipeater that DOES decode and then retransmit the packet to
NOT qualify as a "repeater" by the FCC's definition?

If that is the case... let's say that I took one of these new simplex
VOICE repeaters.. you know.. the ones that digitize the voice, store it
in memory, and then play it back as soon as the person talking dekeys, to
also not qualify as a "repeater" under the FCC's definition?  After all,
it is really doing the same thing that a "digipeater" is doing right?

Taking this one step further.. let's say that we take one of the above
systems, and hook it up to a full duplex voice repeater.

1.  The audio comes in.  It runs through an A/D process and is turned
    into "bits" and is stored in RAM.
2.  100 milliseconds later, this data is fed back to a D/A and is restored
    to analog form (i.e. AUDIO) and is fed to the repeater transmitter.

Now we have a voice system that takes a voice... encodes it, throws in a
time delay, decodes it, and retransmits it... this system seems to be to
me, identical to what a "digipeater" does, and yet maybe then IT might not
qualify as a "repeater" by the FCC's definition either?   Ummm... Ahhhh....

I know that it is not advantageous to argue that a "digipeater" is
automatically retransmitting, as it opens up a whole can of worms, but
logically it seems to me that the matter of "decoding and reconstruction"
is a pretty weak point to base a discussion on whether a "digi" is really
a repeater or not.   No flames intended... show me the error of my ways.

Mark Bitterlich
[e-mail]
[e-mail]

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

Date: Sat, 2 May 1992 23:53:16 GMT
From: sdd.hp.com!hpscdc!hplextra!hpfcso![e-mail]
Subject: KA9Q for the Hp 48sx??
To: [e-mail]

In rec.radio.amateur.packet, [e-mail] (Jason A Kronz) writes:

> Yesterday another HAM told me that there was a HP 48sx version of KA9Q packet
> program.  Does anyone know where or how I can get this??? I really want a
> complete protable packet station ie ht,hp48,and TNC.  Well if anyone can help
> I'd appreciate it.  Thanks.
>                                         -jason kronz (N9OFN)

    WA7NWP aka Bill Vodall demonstrated his 48SX "pocket packet"
    station a couple of weeks ago at our weekly ham radio lunch.

    He can be reached at [e-mail].

---
Dave Jobusch            3404 E. Harmony Road MS#99      [e-mail]
Hewlett-Packard         Fort Collins, CO 80525-9599     david_jobusch@hp4000
UDL Workstation Kernel  T/303-229-6637                  N0OJD

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

Date: 2 May 92 14:24:11 GMT
From: swrinde!zaphod.mps.ohio-state.edu!menudo.uh.edu!lobster!n5abi![e-mail]
Subject: police MDT's
To: [e-mail]

[e-mail] writes:

> Does anybody know the actual data protocol for police MDT's? The police have
> quit using their radios in town here and started installing MDT's in their
> cars about 9 months ago. What frequencies do they use?

  The protocol used depends on which company they buy the MDT
from. Each has it's own protocol and they are not a "standard"
type protocol. They can be on any of the normal frequencies, but
most I have seen are now using the 800 meg range.

-----------------------------------------------------------------------
      Gene Kennedy - Ham Radio Operator, N5ABI -
              [e-mail]
-----------------------------------------------------------------------

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

Date: 2 May 1992 22:37:20 -0700
From: [e-mail]
Subject: WNOS-4 and the PI card..
To: [e-mail]

Hello in reply to this question.
the version wnos 3b1 dont have PI support
wnos 4 dont have this card either.. but can build it in.. if you need
just gota ask..
if you can mail me on the internet with a internet reply address
ill add you to the digest listserv.. then you get the latest info on
wnos daily..
barry  wnos beta tester support.  DC0HK / G8SAU
[e-mail]  Subject: wnos-group Text: SUBSCRIBE <your email address>
enjoy.

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

End of Packet-Radio Digest V92 #118
******************************
Date: Mon,  4 May 92 04:30:03 PDT
From: Packet-Radio Mailing List and Newsgroup <[e-mail]>
Errors-To: [e-mail]
Reply-To: [e-mail]
Precedence: Bulk
Subject: Packet-Radio Digest V92 #119
To: packet-radio


Packet-Radio Digest         Mon,  4 May 92       Volume 92 : Issue 119

Today's Topics:
              Explanation of Packet FAQ
            PK232 not transmitting
                pk232 problem

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: 3 May 1992 15:16:04 -0500
From: sdd.hp.com!zaphod.mps.ohio-state.edu!moe.ksu.ksu.edu!matt.ksu.ksu.edu![e-mail]
Subject: Explanation of Packet FAQ
To: [e-mail]

I have started posting the packet-FAQ again after some prodding from
Paul Schleck and others.  I am now setting up auto-posting
for the Packet FAQ.  Updates should occur on the 1st & 15th of each
month.

No changes have been made to the FAQ since November 1991.
However, I have not lost all the information/corrections that
have been sent to me.  They will get applied soon.


-Steve Schallehn KB0AGD


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

Date: Sun, 03 May 92 18:22:32 GMT
From: netcomsv!mork![e-mail]
Subject: PK232 not transmitting
To: [e-mail]

I am having a problem getting my W2A to transmit while connected to my
PK232.  I bought the cable from AEA and it seems to be connected properly,
but I'm not sure that the PK232 is putting out the right PTT signals.  If I
have the 232 setup for positive PTT then I get about .1 volt between ground
and the PTT line ( pins 4 and 5 on the connector) during receive and -.1
volts during transmit.  If I go to negative PTT then its 0 volts during
receive and 1.3 volts during transmit.  I think that either one of the
diodes or a transistor has gone bad.  I have the service manual with the
diagrams, but it has been a few years since I have done any circuit
analysis.  I would appreciate any help that I can get on this.  Also, if
you have a PK232 and would be willing to take the above reading for me on
your working 232, I would appreciate it.

Jim Chandler
chandler\@netcom.com
jwc\@sactoh0.sac.ca.us
KD6IRV

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

Date: Sun, 3 May 92 18:42:11 GMT
From: pacbell.com!pacbell!sactoh0![e-mail]
Subject: pk232 problem
To: [e-mail]

I am having a problem getting my W2A to transmit while connected to my
PK232.  I bought the cable from AEA and it seems to be connected properly,
but I'm not sure that the PK232 is putting out the right PTT signals.  If I
have the 232 setup for positive PTT then I get about .1 volt between ground
and the PTT line ( pins 4 and 5 on the connector) during receive and -.1
volts during transmit.  If I go to negative PTT then its 0 volts during
receive and 1.3 volts during transmit.  I think that either one of the
diodes or a transistor has gone bad.  I have the service manual with the
diagrams, but it has been a few years since I have done any circuit
analysis.  I would appreciate any help that I can get on this.  Also, if
you have a PK232 and would be willing to take the above reading for me on
your working 232, I would appreciate it.
--
Jim Chandler
[e-mail]
[e-mail]
[e-mail]

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

End of Packet-Radio Digest V92 #119
******************************
Date: Tue,  5 May 92 04:30:02 PDT
From: Packet-Radio Mailing List and Newsgroup <[e-mail]>
Errors-To: [e-mail]
Reply-To: [e-mail]
Precedence: Bulk
Subject: Packet-Radio Digest V92 #120
To: packet-radio


Packet-Radio Digest         Tue,  5 May 92       Volume 92 : Issue 120

Today's Topics:
ARRL's "Business Rule" proposal - automatic retransmission prohibited?
              HELP ka9q & netrom
                 police MDT's
               WNOS-4 and the PI card..

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: Mon, 4 May 1992 19:18:50 GMT
From: sdd.hp.com!hpscdc!hplextra!hpl-opus!hpnmdla![e-mail]
Subject: ARRL's "Business Rule" proposal - automatic retransmission prohibited?
To: [e-mail]

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

>AL N1AL replies to a previous posting, which in the name of brevity is
>not included with:

>>If you send packet through a voice repeater (or any other repeater that
>>does not decode the packet and then reconstruct it before transmission),
>>then I believe it would qualify as a "repeater" by FCC's definition.

>Al, then I would assume by this that you would consider a "normal" (sic)
>packet node/digipeater that DOES decode and then retransmit the packet to
>NOT qualify as a "repeater" by the FCC's definition?

Right

>If that is the case... let's say that I took one of these new simplex
>VOICE repeaters.. you know.. the ones that digitize the voice, store it
>in memory, and then play it back as soon as the person talking dekeys, to
>also not qualify as a "repeater" under the FCC's definition?  After all,
>it is really doing the same thing that a "digipeater" is doing right?

As with any law, there are going to be grey areas.  I think your example
still qualifies as a repeater.  The reason it is different than the
packet digipeater is that in your example, the retransmitted signal is a
reconstruction of the actual modulation of the original.  If there is
distortion on the original signal, it will be retransmitted with the
distortion intact.  If effect, you have just changed the modulation
mode -- from analog to digital and back again.

The packet digipeater actually decodes the packet down to the raw information
level.  If there is distortion on the original signal, it is removed.
In fact, the data rate of the output doesn't even have to equal the rate
of the input.  The voice equivalent would be to have a speech-recognition
system that decodes the words (say into an ASCII file) and then uses
a voice encoder to regenerate the message.

Or, to use currently available technology, the voice equivalent would be
to have a human decode the message and read it back on another frequency.
(In other words, traffic handling.)

Al N1AL

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

Date: 4 May 92 18:40:28 GMT
From: [e-mail]
Subject: HELP ka9q & netrom
To: [e-mail]

 Yes still struggling with ka9q, latest problem:

 Unable to use netrom node to digi a tcpip connection.
Thanks to wd6ehr have setup the "netrom ...", "route ..." & "arp ..." to get
ka9q to transmit the packet thru the netrom node. However the tcpip station
on the other end never responds. The trace of the packet shows the ip
section with the correct ip # for the other end but my ip # is 0.0.0.0 and
i suspect thats the problem. Anyone verify that my ip # should not be 0.0.0.0?
And even better yet what am i missing in autoexec that gives me zero's?
 Spent some time in the source trying figure out where the 0's come from but
its not imediately obvious. As an alternate can someone give me some pointers
on where to look in the source? Now where is phil when you need him :-)
hmmmm oh yes still hoping netrom will go away.
Unfortunately i think its the only way for me to get out of the valley :-(.
 FYI if i can connect direct i have no problems with tcpip its thru the
netrom node that things get one way :-(.
73, ted
n6trf

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

Date: 5 May 92 07:25:54 GMT
From: swrinde!mips!spool.mu.edu!sol.ctr.columbia.edu!destroyer!ais.org![e-mail]
Subject: police MDT's
To: [e-mail]

In article <[e-mail]> [e-mail] (Gene A. Kennedy) writes:
>[e-mail] writes:
>
>> Does anybody know the actual data protocol for police MDT's? The police have
>> quit using their radios in town here and started installing MDT's in their
>> cars about 9 months ago. What frequencies do they use?
>
>  The protocol used depends on which company they buy the MDT
>from. Each has it's own protocol and they are not a "standard"
>type protocol. They can be on any of the normal frequencies, but
>most I have seen are now using the 800 meg range.
>
>-----------------------------------------------------------------------
>          Gene Kennedy - Ham Radio Operator, N5ABI -
>                      [e-mail]
>-----------------------------------------------------------------------

    In addition to the proprietary data format most state/federal law
enforcement agencies which manage the typical law enforcement data networks
require that if an agency is going to tie in their MDT system with the
state/federal database network, the RF link for the MDTs MUST be encrypted.


--
 Tim Tyler   Internet: [e-mail]  MCI Mail: 442-5735  C$erve: 72571,1005
P.O. Box 443     Packet: KA8VIR @KA8UNZ.#SEMI.MI.USA.NA
Ypsilanti MI
48197-0443                  PADI, USPA, AFCEA, INEOA, P226, VFR700, etc.

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

Date: Mon, 4 May 92 15:24:31 GMT
From: usc!cs.utexas.edu!utgpu!cunews!nrcnet0!dgbt![e-mail]
Subject: WNOS-4 and the PI card..
To: [e-mail]

In article <[e-mail]> [e-mail] (BARRY TITMARSH) writes:
>Hello in reply to this question.
>the version wnos 3b1 dont have PI support
>wnos 4 dont have this card either.. but can build it in.. if you need
>just gota ask..

Another option for using the PI card with versions of NOS which lack the
built-in driver: if it has packet driver support compiled in (most versions
do, it seems), you can use the PI packet driver instead.  The latest release
can be found in pi_dvr3.zip, on hydra.carleton.ca or ucsd.edu.

Barry VE3JF
--
Barry McLarnon                  |  Internet: [e-mail]
Communications Research Center  |  AMPRnet: [e-mail]
Ottawa, Canada  K2H 8S2         |  PBBSnet: ve3jf@ve3jf.#eon.on.can

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

End of Packet-Radio Digest V92 #120
******************************
Date: Wed,  6 May 92 04:30:03 PDT
From: Packet-Radio Mailing List and Newsgroup <[e-mail]>
Errors-To: [e-mail]
Reply-To: [e-mail]
Precedence: Bulk
Subject: Packet-Radio Digest V92 #121
To: packet-radio


Packet-Radio Digest         Wed,  6 May 92       Volume 92 : Issue 121

Today's Topics:
ARRL's "Business Rule" proposal - automatic retransmission prohibited?
            Help with Baycom Packet Modem

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 May 92 15:23:58 GMT
From: dog.ee.lbl.gov!nosc!crash!telesoft![e-mail]
Subject: ARRL's "Business Rule" proposal - automatic retransmission prohibited?
To: [e-mail]

In <[e-mail]> [e-mail] (Alan Bloom) writes:
>A voice repeater retransmits the signal AS IT IS RECEIVED.  You can think
>of the repeater as a bent pipe that takes the input signal and sends it
>out again unmodified.

There's nothing in the definition of "repeater" in the rules that says a
repeater can't have a time delay or how long the delay can be.  It just says:

(97.3a24) "Repeater.  An amateur station that automatically retransmits the
signals of other stations."

>A digipeater does the same thing an old-time traffic handler does.
>It receives the message (packet), stores it, and re-sends it later.
>I believe that the FCC definition of "repeater" no more applies to
>packet digipeaters than it would to traffic handlers.

Old-time traffic handlers don't "automatically retransmit".  The rules don't
say that it how much delay there is going thru the (audio or digital)
repeater, or whether the signals are modified going thru the repeater (such
as adding a PL on the output, filtering out audio below 300 hz or above 3000
hz, setting the digipeated bit in a packet, etc), they don't say you can't
convert the audio signal to digital and back to audio again.

--GaryM
--
Gary Morris KK6YB             Internet: [e-mail]
TeleSoft                      Packet:   KK6YB@W2XO or KK6YB@KC6NZN
San Diego, CA USA             Phone:    [phone] x128

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

Date: Tue, 5 May 1992 18:45:02 GMT
From: ftpbox!news.acns.nwu.edu![e-mail]
Subject: Help with Baycom Packet Modem
To: [e-mail]

I was recently given a Baycom Packet Modem.  The device appears to have
never been used and the diskette that came with it contains some
documentation files.

A 4 wire telephone cable with a modular telephone plug on one end and open
wires on the other end was supplied with the modem.  The documentation from
the diskette does not mention how to wire these 4 leads to control the
earphone, microphone and PTT of the radio.

If anyone has the information about connecting this device to a radio (I
plan to use a Yaesu FT-470) please email to me at:

[e-mail]

Thanks es 73,

Greg Lapin, KD9AZ

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

End of Packet-Radio Digest V92 #121
******************************
Date: Thu,  7 May 92 04:30:03 PDT
From: Packet-Radio Mailing List and Newsgroup <[e-mail]>
Errors-To: [e-mail]
Reply-To: [e-mail]
Precedence: Bulk
Subject: Packet-Radio Digest V92 #122
To: packet-radio


Packet-Radio Digest         Thu,  7 May 92       Volume 92 : Issue 122

Today's Topics:
       Connecting the PAKRATT 232 MBX to the TS 690S. (2 msgs)
                   ft -470
         PK232 with G3RUH ? Anyone? (2 msgs)
                 TAPR

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: 6 May 92 20:48:46 GMT
From: swrinde!mips!spool.mu.edu!tulane!rouge!pc.usl.edu![e-mail]
Subject: Connecting the PAKRATT 232 MBX to the TS 690S.
To: [e-mail]

In article <[e-mail]> [e-mail] ([e-mail] , VY2DCS) writes:
>I have a question with regards to linking the 232mbx to the 690s using
>the ACC2 port. I have had no problems with the receive part of the
>connectors BUT have had no luck in being able to get the 232 to
>activate the transmit (PTT)line on the 690. The loop test with the 232 indicates
>that all is fine with the audio output of the 232. In the manual the red or
>number 5 wire is to be attched to pin 13 of the ACC2. AeA reps have
>indicated that it can be attached to pin 9 instead. I've tried both and
>have been unable to get the 2323 to activate the transmit action of the
>690s even with the mic gain full open, and the AFSK output of the 232
>turned full open. All other settings indicated in the manual for the rig
>were followed. Yet NO power output or ALC action  was displayed on the front
>panel when I throw the 232 into the transmit mode ( using  "K" when in

David, while I don't have a ts690, I do have a ts440s interfaced via the
ACC2 jack.  What I found, was that by tieing the tnc's PTT output to both
the mike mute as well as radio ptt, I was muting the audio fed into the
ACC2 jack.  I had to use diode isolators to make it work right.  Could
this be your problem?

73,
--
-- James Dugal, N5KNX           Internet: [e-mail]
Associate Director              Ham packet: n5knx @k5arh (land), UO-22 (sat.)
Computing Center                US Mail: PO Box 42770  Lafayette, LA  70504
University of Southwestern LA.  Tel. [phone]       U.S.A.

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

Date: 6 May 92 22:33:37 GMT
From: rudy.rutgers.edu!pilot.njin.net![e-mail]
Subject: Connecting the PAKRATT 232 MBX to the TS 690S.
To: [e-mail]

> connectors BUT have had no luck in being able to get the 232 to
> activate the transmit (PTT)line on the 690. The loop test with the 232 indicates

I don't know about the 690, but on the 440 it is IMPERATIVE that
you move the PTT/VOX - OFF SEMI FULL QSK switch off the left
most position.

-Ron

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

Date: 6 May 92 14:25:27 GMT
From: usc!zaphod.mps.ohio-state.edu!mips!darwin.sura.net!tulane!rex!agwbbs![e-mail]
Subject: ft -470
To: [e-mail]

In a message dated Tue  5 May 92 22:50, [e-mail] (gregory
wrote:

 L> If anyone has the information about connecting this device to a radio
 L> (I
 L> plan to use a Yaesu FT-470) please email to me at:

Hi Greg,

 You connect a 2.2k Resistor for the push-to-talk and a .01 cap. for the
mike audio to the tip of the Mike Plug. That should work just fine..

73 de Angelo


-- Via DLG Pro v0.991

Internet:[e-mail]
  Usenet:rex!agwbbs!angelo_glorioso_III
  Packet:N5UXT @ N5UXT.#NOLA.LA.USA.NA
  Tcp/ip:N5UXT.AMPT.ORG  [44.108.2.13]

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

Date: 6 May 92 20:42:12 GMT
From: swrinde!mips!spool.mu.edu!tulane!rouge!pc.usl.edu![e-mail]
Subject: PK232 with G3RUH ? Anyone?
To: [e-mail]

In article <[e-mail]> [e-mail] (Markus Lamminmaki) writes:
>Has anyone used PK232 with G3RUH 9600 baud modem? I would be interested
>to get info about the modifications for PK232 to get this beast working
>with 9600 baud.

I read some messages on UO-22 (or 14?) which indicated that it's been done.
But there were complaints that the async interface, running at 9600 baud,
was slow to empty the PK232 buffers, leading to some frustrating xmit
delays. But, I have no personal experience to relate.  I run my MFJ1270b
at 19.2kb and have no complaints (save the faulty MFJ kiss implementation;
use tapr 1.1.7b instead).

73,
--
-- James Dugal, N5KNX           Internet: [e-mail]
Associate Director              Ham packet: n5knx @k5arh (land), UO-22 (sat.)
Computing Center                US Mail: PO Box 42770  Lafayette, LA  70504
University of Southwestern LA.  Tel. [phone]       U.S.A.

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

Date: 7 May 92 03:30:25 GMT
From: swrinde!mips!darwin.sura.net!tulane!rex!agwbbs![e-mail]
Subject: PK232 with G3RUH ? Anyone?
To: [e-mail]

In a message dated Wed  6 May 92 16:44, [e-mail] (dugal James P.)
wrote:

 JJP> I read some messages on UO-22 (or 14?) which indicated that it's
 JJP> been done.
 JJP> But there were complaints that the async interface, running at 9600
 JJP> baud,
 JJP> was slow to empty the PK232 buffers, leading to some frustrating
 JJP> xmit
 JJP> delays. But, I have no personal experience to relate.  I run my
 JJP> MFJ1270b
 JJP> at 19.2kb and have no complaints (save the faulty MFJ kiss
 JJP> implementation;
 JJP> use tapr 1.1.7b instead).

 Hi James. I just read your message about you running at 19.2k with an
MFJ-1270B. How are you doing this?? What are you using for a Radio?? What
modems
are you using???

 We are about to start testing with 9600 baud G3RUH Modems with MFJ-1270
tnc and commerical radios... I was wondering if you had any suggestion or
ideas?

 You also mentioned about getting rid of the MFJ kiss and go with the
TAPR 1.1.7B code.. How did you do this?? Did you order the chip?? Do you
have
the code on disk???

 We are going to try and develop a 9600 UHF Backbone link from here to
texas
with a little luck..

Any Help on Radios that work or ANYTHING, PLEASE SEND IT!!

73 de Angelo


-- Via DLG Pro v0.991

Internet:[e-mail]
  Usenet:rex!agwbbs!angelo_glorioso_III
  Packet:N5UXT @ N5UXT.#NOLA.LA.USA.NA
  Tcp/ip:N5UXT.AMPT.ORG  [44.108.2.13]

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

Date: 6 May 1992 04:30:41 -0700
From: [e-mail]
Subject: TAPR
To: [e-mail]

Hello, who knows where to find the latest version of TAPR to be used in a
TNC2C?

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

End of Packet-Radio Digest V92 #122
******************************
Date: Fri,  8 May 92 04:30:02 PDT
From: Packet-Radio Mailing List and Newsgroup <[e-mail]>
Errors-To: [e-mail]
Reply-To: [e-mail]
Precedence: Bulk
Subject: Packet-Radio Digest V92 #123
To: packet-radio


Packet-Radio Digest         Fri,  8 May 92       Volume 92 : Issue 123

Today's Topics:
            Access to internal DSP
      ARRL's "Business Rule" proposal - automatic retransmission
ARRL's "Business Rule" proposal - automatic retransmission prohibited? (2 msgs)
             Digicom Availability
             Direct FSK on Ramsey FX-440
              IC-32AT for Packet
        New TAPR 9600 BAUD modem and the TNC-1
                  NOS, etc.
             Police MDTs (2 msgs)
                 TAPR

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: 6 May 92 21:28:35 GMT
From: siemens!cadillac.siemens.com![e-mail]
Subject: Access to internal DSP
To: [e-mail]

An off the wall question...

I'm considering the purchase of a TNC. I would like to go DSP,
but am concerned about the cost. I can more easily justify the
cost (and slow down my racing pulse!) if I can find more than
one use for the DSP portion of the TNC. The final Jeopardy
question...

  Can I use the DSP portion of the AEA or Grace unit for vanilla
  audio processing? Are there input/output filters to be disabled
  or circumvented? Can the sampling rates be adjusted? What is
  the resolution?

Well, that was four questions. I might want to try voice or, gasp,
music processing/synthesis with the DSP as well as push bits into
the ether.



--
paul j. drongowski                N2OQT
siemens corporate research inc    [e-mail]
princeton, new jersey 08540       [phone]

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

Date: 7 May 1992 04:02:47 -0700
From: [e-mail]
Subject: ARRL's "Business Rule" proposal - automatic retransmission
To: [e-mail]

 Comparing digital repeaters of _any_ sort with voice repeaters is
like comparing apples with orangutans - other than their both being
organic, they have little in common, and rules that make perfect sense
for the one (i.e. an apple a day keeps the Doctor away, but may be
harmful to those sensitive to alar) make little sense when applied to
the other.  (I understand that orangutans protest most vehemently
while being consumed)

 This is why the FCC is rewriting rules pertaining to amateur packet.

 We've opened a whole new can of worms, and the old rules, intended
for CW, live operators, NBFM voice repeaters, HF SSB operators, ATV,
live RTTY, etc., don't make a lot of sense when applied to digital
networking systems.  That is why you all (well - MOST of you) have
sensible, valid points, yet unequivocally contradict one another.

 I'm OK - you're so-so; but the rules stink on ice.

 --
 Mike   wd6ehr.ampr.org![e-mail]

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

Date: 6 May 92 14:11:47 GMT
From: idacrd![e-mail]
Subject: ARRL's "Business Rule" proposal - automatic retransmission prohibited?
To: [e-mail]



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

Date: 7 May 1992 16:35:14 GMT
From: ucsd.edu![e-mail]
Subject: ARRL's "Business Rule" proposal - automatic retransmission prohibited?
To: [e-mail]

In article <[e-mail]> [e-mail] (Bob McGwier) writes:
>If you want to get REALLY picky, a digipeater does NOT just retransmit
>the data as received.  It sets a single bit in the address fields saying
>that it (the digi) has successfully received and digipeated the packet.

And then it recalculates the CRC, so the packet that leaves a digipeater
really isn't close to the one that came in to it - at least three bytes
have changed, and it wasn't in real-time, and the channel contention has
been done all over again, and like wow.
    - Brian

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

Date: 7 May 1992 12:22:00 -0700
From: [e-mail]
Subject: Digicom Availability
To: [e-mail]

Hello!
       I'm trying to put together a packet station from scratch after getting
interested in it through reading. My budget is tiny :-), so I've obtained a
secondhand Commodore 64 and am aiming at getting licensed in November when
the next Uk Radio Amateurs Exam happens. In the meantime I'm looking for the
Digicom software and construction details/schematic for its associated Bell 202
modem.

Can anyone send these to me or post info on where they can be obtained by ftp
or mail file-server? The C64 will soon have an RS232 interface and then C64/128
Kermit, so downloads should be possible.

I'm interested in TCP/IP but participation in AMPRNET will have to wait until
PC prices go lower.

Thanks in Advance!
          Steve Rudman

PS If I've assumed wrong and Digicom is *not* freely copyable for am rad
purposes then the address of a dealer stocking it in the UK would be useful.

 Janet:  "hooke::icarus::rudman" @ uk.ac.ox.atm.isams
-or-
 Janet:  umeeb37 @ uk.ac.ic.cc.vaxa   (if my local host is down)

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

Date: 7 May 92 20:49:26 GMT
From: pa.dec.com!nntpd2.cxo.dec.com!nntpd.lkg.dec.com!carafe.enet.dec.com![e-mail]
Subject: Direct FSK on Ramsey FX-440
To: [e-mail]

Well, old Mr. Klutz here is trying his unsteady hand at assembling
a Ramsey FX-440!  I'm still trying to find the Heath-style lug strips
and tube socket pins, but seriously, folks, it's a clever design.  The
receiver is based around the Motorola MC3335 dual conversion chip.
That's a step up, they claim, from the older MC3359 in the older kits.

Anyway, I see that this new kit has a neat feature.  Not only does
it have a 5-pin DIN packet connector (as well as mic and speaker
jacks), but it has three different output options.  One is the
speaker output, just the thing for your old 1200 bps slow modems
and TNCs.  One is the raw discriminator, just the thing for your
existing packet modems.  The third is FSK demodulated by the 3335!
Ramsey claims (this using a Murata "F" i-f filter, maybe 16 kHz)
that it'll work to 35000 bps, though 9600 seems a design center.

Has anyone tried this?  The transmit side is direct FM applied to the
VCO, so it probably has a low-end cutoff caused by the synthesizer loop
bandwidth, but given HDLC at even 1200 bps, that probably won't break
it, though they don't tell you the loop characteristics.  The main
issue is that there's no scrambling, but then HDLC and NRZI do a little
on their own.

For under $200, modem included, this could be a great bargain for
packeteers.  If you don't get burned (literally) trying to solder it
together, and if it works as well as I'd like it to.
---
Fred R. Goldstein   [e-mail]
k1io             or [e-mail]   voice:[phone]
Standard Disclaimer:  Opinions are mine alone; sharing requires permission.

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

Date: 7 May 1992 06:36:04 -0700
From: [e-mail]
Subject: IC-32AT for Packet
To: [e-mail]

 What resistors, caps are suggested to use the IC-32AT on Packet.  My
Alinco DR-110T works just fine, but thinking of a portable set up.
Thanks.
KA2Y@WB2PSI.#WNY.NY.USA.NOAM
Bitnet cellis@brockvma

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

Date: Fri, 8 May 1992 08:23:51 GMT
From: news.hawaii.edu!mpg.phys.hawaii.edu![e-mail]
Subject: New TAPR 9600 BAUD modem and the TNC-1
To: [e-mail]

I'm trying to hook up TAPR's new 9600 BAUD modem kit to a TNC-1.  The
manual states that connection to a TNC-1 requires a modification in the
switching logic by using different chips on the modem.  When I called TAPR
today I was told that the chips to be used with the TNC-1 aren't available yet
(and may not be for a while).

I'm curious though.  What kinds of differences exist between the modem
signalling on a TNC-1 and that of a TNC-2 (which the new modem kit was designed
for)?  I thought the modem disconnect headers were essentially the same on
both models?


--
Antonio Querubin
[e-mail] / [e-mail] / [e-mail]

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

Date: 7 May 92 01:55:03 GMT
From: newsserver.pixel.kodak.com!laidbak!tellab5!vpnet!vpnet![e-mail]
Subject: NOS, etc.
To: [e-mail]

Hi Fred. tcp/ip is alive and well in Chicago. Welcome back
(almost). There are about a zillion modifications of the
original ka9q net program. I run PA0GRI (grinos) ver. 2.0j
which offers a split screen ability. I also like wnos3.0
but it has some shortcomings. Since all my internet access
is via packet, I can't ftp but there are several sources
around Chicago.
Ken wa9wcp@wa9aek or ax25 @ W9ZMR.IL

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

Date: 7 May 92 04:26:57 GMT
From: sdd.hp.com!usc!rpi!masscomp!ocpt!tsdiag!ka2qhd![e-mail]
Subject: Police MDTs
To: [e-mail]

Ofcourse only police could possibly be skilled enough to
use these mdt's (gawd i hate to think what they cost us in
tax dollars) but does anyone know if theres a reasonably
inexpensive version for our mobile use? (yea i know, get a
cheap laptop) seriously, does anyone know of a small dumb
type terminal for mobile use? Surely somewhere in asia they
muse be made. ?

tnx in advance, johnd

(ofcourse, i'll make my spouse drive while i type. 8-))

--

UUCP: rutgers!ka2qhd!johnd - - - - - or - - - - -  Domain: [e-mail]

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

Date: 7 May 92 20:43:03 GMT
From: rudy.rutgers.edu!pilot.njin.net![e-mail]
Subject: Police MDTs
To: [e-mail]

Radio Snack Model 100's are pretty nice for this app if you can still
find them.

-Ron

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

Date: Fri, 8 May 1992 08:14:18 GMT
From: news.hawaii.edu!mpg.phys.hawaii.edu![e-mail]
Subject: TAPR
To: [e-mail]

In article <[e-mail]> [e-mail] (Wim Nijntjes) writes:
>Hello, who knows where to find the latest version of TAPR to be used in a
>TNC2C?

The latest version is 1.1.7b and you can 'FTP' it from tomcat.gsfc.nasa.gov.
It's in the tapr directory as a ZIP file.  You'll need an EPROM programmer of
course...
--
Antonio Querubin
[e-mail] / [e-mail] / [e-mail]

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

Date: (null)
From: (null)
If you want to get REALLY picky, a digipeater does NOT just retransmit
the data as received.  It sets a single bit in the address fields saying
that it (the digi) has successfully received and digipeated the packet.


Bob


















This is the way we screw our mailer.

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

End of Packet-Radio Digest V92 #123
******************************
Date: Sat,  9 May 92 04:30:02 PDT
From: Packet-Radio Mailing List and Newsgroup <[e-mail]>
Errors-To: [e-mail]
Reply-To: [e-mail]
Precedence: Bulk
Subject: Packet-Radio Digest V92 #124
To: packet-radio


Packet-Radio Digest         Sat,  9 May 92       Volume 92 : Issue 124

Today's Topics:
               HamNet? (3 msgs)
           MFJ1278 firmware patch: Hostmode
                 Police MDTs
                TAPR (2 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: 8 May 92 14:53:52 GMT
From: swrinde!zaphod.mps.ohio-state.edu!moe.ksu.ksu.edu!mdsol1!news.byu.edu!news.mtholyoke.edu![e-mail]
Subject: HamNet?
To: [e-mail]

Hi.  I know nothing about Ham radios, I'm inquiring for a
person who doesn't have access to this net (yet).

He's heard of something like a computer network for Ham
radio operators.  I've yet to find anything of the sort!
Anyone out there have any clue as to what he's talking about?

Thanks

Karen

--
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
:)      Karen M. Bourque         ********    [e-mail] (:
:)      User Services Consultant ********    [e-mail]        (:
:)      CIS - Mount Holyoke College - South Hadley, Massachusetts - USA (:

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

Date: 8 May 92 17:05:40 GMT
From: rudy.rutgers.edu!pilot.njin.net![e-mail]
Subject: HamNet?
To: [e-mail]

The qusetions a bit vague, but you've found one of the discussion
groups (USENET / INTENET /BITNET).  There's also a HAM forum (HAMNET)
on CompuServe, plus numerous other Bulletin boards, plus a system
of Bulletin boards run by hams that actually use ham radio to send
the messages around rather than phones.

-Ron

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

Date: 8 May 92 19:24:32 GMT
From: [e-mail]
Subject: HamNet?
To: [e-mail]

In article <[e-mail]> [e-mail] (Ron) writes:
>The qusetions a bit vague, but you've found one of the discussion
>groups (USENET / INTENET /BITNET).  There's also a HAM forum (HAMNET)
          ^^^ Internet (typo)
>on CompuServe, plus numerous other Bulletin boards, plus a system
>of Bulletin boards run by hams that actually use ham radio to send
>the messages around rather than phones.
>
>-Ron

Unless, of course the original poster ([e-mail]) meant
computer networks that use Ham radio as part of the transport mechanism
(e.g., TCP-IP) instead of "networks of people talking about ham radio."

                    --Rick
                      N3JGF

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

Date: Sat, 9 May 1992 02:46:53 GMT
From: usc!rpi!uwm.edu!linac!att!cbfsb!cbnewsb.cb.att.com![e-mail]
Subject: MFJ1278 firmware patch: Hostmode
To: [e-mail]

copied from packet:
 Msg# TSF  Size #Rd  Date  Time From   MsgID        To
10077 BF   6074   0 28-Apr 1741 IK1SHJ 6316_I1HUH   INFO@WW ()
 Sb: HOSTMODE for MFJ1278 NEW

   LIST OF PATCHES FOR USING WA8DED HOSTMODE FIRMWARE VER 2.6
          WITH MFJ 1278 MULTIMODE TNC

ADDRES     ORIG.  PATCH     !      ADDRES     ORIG.  PATCH
---------------------------------------------------------
 0001:      CD      B4      !      61BA:              27
 0002:      00      61      !      61BB:              D3
 0108:      03      DF      !      61BC:              7F
 010D:      03      DF      !      61BD:              3E
 011B:      01      DD      !      61BE:              00
 0120:      01      DD      !      61BF:              D3
 01F5:      01      DD      !      61C0:              FB
 022D:      03      DF      !      61C1:              C3
 025A:      02      DE      !      61C2:              CD
 026B:      03      DF      !      61C3:              00
 0270:      03      DF      !      61C4:              C5
 02B6:      02      DE      !      61C5:              01
 0331:      03      DF      !      61C6:              10
 033B:      02      DE      !      61C7:              27
 0354:      03      DF      !      61C8:              3A
 0362:      01      DD      !      61C9:              33
 0396:      01      DD      !      61CA:              93
 03A0:      01      DD      !      61CB:              CB
 03AC:      00      DC      !      61CC:              4F
 03BD:      01      DD      !      61CD:              C2
 03C2:      01      DD      !      61CE:              00
 03DC:      01      DD      !      61CF:              70
 0423:      00      DC      !      61D0:              CB
 0457:      01      DD      !      61D1:              47
 0459:      01      DD      !      61D2:              20
 045E:      01      DD      !      61D3:              08
 0483:      03      DF      !      61D4:              CB
 0496:      02      DE      !      61D5:              6F
 04D5:      03      DF      !      61D6:              20
 04DE:      02      DE      !      61D7:              08
 050A:      01      DD      !      61D8:              CB
 0511:      01      DD      !      61D9:              F1
 0515:      01      DD      !      61DA:              18
 0525:      01      DD      !      61DB:              04
 053B:      01      DD      !      61DC:              CB
 053E:      00      DC      !      61DD:              E9
 0542:      01      DD      !      61DE:              CB
 0557:      01      DD      !      61DF:              D8
 055C:      01      DD      !      61E0:              CB
 0561:      00      DC      !      61E1:              67
 057A:      03      DF      !      61E2:              28
 058B:      03      DF      !      61E3:              02
 0592:      01      DD      !      61E4:              CB
 05A3:      01      DD      !      61E5:              88
 05DD:      3A      C3      !      61E6:              78
 05DE:      33      C4      !      61E7:              D3
 05DF:      93      61      !      61E8:              7F
 05E0:      D3      00      !      61E9:              79
 05E1:      20      00      !      61EA:              D3
 61B4:              F3      !      61EB:              BF
 61B5:              3E      !      61EC:              C1
 61B6:              50      !      61ED:              3A
 61B7:              D3      !      61EE:              33
 61B8:              BF      !      61EF:              93
 61B9:              3E      !      61F0:              C9

 NOTES:
 1) This is only a PATCH to WA8DED firmware for using it with
    MFJ 1278 TNCs.  The resultant code is still copyrighted
    by Ronald E. Raikes.
 2) Code from 61B4 to 61F0 is added to the bottom of the
    original firmware so the original data is unknown.
 3) BE SURE TO PATCH THE SAME VERSION
    these patches only work with the listed version
    (Check for original values to match with the listed ones.)
 4) You can program this code on a 27C256 EPROM but in such
    case you must leave PIN 1 of the IC OUT OF THE SOCKET and
    wire it to +5 Volts (PIN 28 of the EPROM).
    If You use a 27C512 program the code IN THE SECOND HALF
    OF THE EPROM (starting from address 8000H).
 5) Remove the original EPROM at position U23 and install
    the WA8DED patched one, the MFJ 1278 will respond
    you as a TNC2 at 9600 BAUD.
    To work at 4800 BAUD Patch  61B6:48  61C6:08
 6) With this FIRMWARE you will lose the multi mode capabilty
    of MFJ 1278, it is intended to allow you to enjoy programs
    like SP in true HOST MODE.
 7) The patches listed are 110 if you read less this message is
    corrupted get a good one.)
 8) The followings new commands are available:

    @R0 (Default)  Select  RADIO 1 port
    @R1            Select  RADIO 2 port

    @A0 (Default)  Select VHF PACKET modem
    @A1            Select  HF PACKET modem

    @X0 (Dfault)   Select 1200 BAUD VHF PACKET modem
    @X1            Select 2400 BAUD VHF PACKET modem (MFJ TURBO ONLY)

    @J  For software experts only Cause a JUMP to location 7000H.
    I have put a EFKISS code here so i have kiss too.
    DONOT USE OR THE TNC WILL HANG
    (The code to be added at location 7000H to get EFKISS is
    available upon request.)

 73 DE Giovanni Bini IK1SHJ@I1HUH.#GE.ITA.EU JN44LJ GENOVA.
    I am in qrt now for info contact IW1QGT@I1HUH.#GE.ITA.EU
======================================================================
I haven't tried or verified this, proceed at your own risk.  WA2ISE

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

Date: 8 May 92 16:45:47 GMT
From: swrinde!gatech!ukma![e-mail]
Subject: Police MDTs
To: [e-mail]

[e-mail] (Ron) writes:

>Radio Snack Model 100's are pretty nice for this app if you can still
>find them.

I have a model 100 I could probably part with!
--
Harold G. Peach, Jr.       ><>       N4FLZ       _%       [e-mail]

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

Date: Sat, 9 May 1992 05:50:32 GMT
From: qualcom.qualcomm.com!qualcom![e-mail]
Subject: TAPR
To: [e-mail]

[e-mail] (Antonio Querubin) writes:

>The latest version is 1.1.7b and you can 'FTP' it from tomcat.gsfc.nasa.gov.
>It's in the tapr directory as a ZIP file.  You'll need an EPROM programmer of
>course...

Actually, as of a week or two ago the latest version is 1.1.8.  Supposedly,
the new version adds a host mode.  I'm still waiting for an electronic
release on CompuServe - one has been promised.  I'm sure it'll be on
tomcat shortly thereafter.

Paul Williamson, KB5MU
[e-mail]

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

Date: 9 May 92 05:15:28 GMT
From: ubc-cs!newsserver.sfu.ca![e-mail]
Subject: TAPR
To: [e-mail]

[e-mail] (Antonio Querubin) writes:

>In article <[e-mail]> [e-mail] (Wim Nijntjes) writes:
>>Hello, who knows where to find the latest version of TAPR to be used in a
>>TNC2C?

>The latest version is 1.1.7b and you can 'FTP' it from tomcat.gsfc.nasa.gov.
>It's in the tapr directory as a ZIP file.  You'll need an EPROM programmer of
>course...
>--
>Antonio Querubin
>[e-mail] / [e-mail] / [e-mail]

Actually TAPR has just released 1.1.8, which can be found on Compuserve
HamNet Forum (GO HAMNET).  I'm sure it'll be available on ham oriented
BBS'es soon too.  1.1.8 fixes some bugs, and adds a new (and different)
host mode interface.  A companion file TNCHST.ZIP (also on CIS HamNet
LIB 9) has info on the host mode, plus some sample software showing it's
use.  73.

Allen Mar
[e-mail]
ve7dpm@ve7kit.#vanc.bc.can.noam (packet mail)

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

End of Packet-Radio Digest V92 #124
******************************
Date: Sun, 10 May 92 04:30:02 PDT
From: Packet-Radio Mailing List and Newsgroup <[e-mail]>
Errors-To: [e-mail]
Reply-To: [e-mail]
Precedence: Bulk
Subject: Packet-Radio Digest V92 #125
To: packet-radio


Packet-Radio Digest         Sun, 10 May 92       Volume 92 : Issue 125

Today's Topics:
            Access to internal DSP
         connecting a Standard HT to a TNC ?
                DSP2232 modems
                   HamNet?
             In-Reply-To: HamNet?
               PacketCluster??
    Ramsey Packet Modem kit ... giving me a carrier tone?

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 May 92 15:29:56 GMT
From: idacrd![e-mail]
Subject: Access to internal DSP
To: [e-mail]



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

Date: Sat, 9 May 1992 15:55:28 GMT
From: usc!zaphod.mps.ohio-state.edu!moe.ksu.ksu.edu!ux1.cso.uiuc.edu!news.cso.uiuc.edu![e-mail]
Subject: connecting a Standard HT to a TNC ?
To: [e-mail]

I suspect that there aren't more articles in rec.radio.amateur.packet
because most packet guys can get their info off of their local packet
networks.  I soon hope to count myself among thee.

(like the Catch-22 for would-be hams in our area... "How do I find out when
the next club meeting is?"  "Just ask somebody on the 2 meter net next week!"
"But I don't have my license yet!" ... "Oh.  Gee I don't know."  :-)  )

((ever heard of the telephone!?  :-) ))

No!  But seriously.  I have a Ramsey Packet modem kit, and I want to connect
it to my Standard HT (Heathkit HW-2-M).  The *classic* packet problem.
I'm a bit nervous about wiring to my HT without being *sure*, but I will
probably try the "generic" (Old ICOM/Yaesu) approach soon anyway:

     AFSK ---------- 0.1 uF ----------|
                      |
     PTT ----------- 33 Kohm --------------------- Mic In


     SPKR ---------------------------------------- SPKR

     GND ----------------------------------------- GND

    (TNC) ---------------------------------------- (HT)

I understand that Kenwood HTs are different.  Has anybody actually hooked up
a Standard HT to a TNC?  Please email me!

Thanks!

73 de kb8cne, Brad Banko

Urbana, Illinois
[e-mail]


====================================================================
Brad Banko, Loomis Lab of Physics, Univ. of Illinois, Urbana
*Email*:  [e-mail],  Amateur Radio:  KB8CNE/9 at 146.76-
  "It's better to burn out than to fade away!"  Queen, A Kind of Magic

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

Date: 8 May 92 15:57:37 GMT
From: idacrd![e-mail]
Subject: DSP2232 modems
To: [e-mail]

Howdy:

I have been on a roll of late.  The KAM killers are done.  I delivered
to AEA all the dual port modems they wanted and am now working on a
couple they didn't ask for, and then finally I will attempt the ones
that are probably not doable.

The DSP2232 now does

dual port VHF/VHF  Packet
dual port VHF/HF   packet
dual port Baudot   / VHF packet
dual port AMTOR    / VHF packet
etc.  All the ones KAM claims in its ads that it alone does.
I am doing some it is not (yet) capable of

dual port 2400/VHF Packet (this is V26B and I will call it that)
dual port V26B/HF packet
dual port Baudot/V26B
dual port AMTOR/V26B.


The ones I think MIGHT be possible, but have not yet attempted include

dual port G3RUH/G3RUH  (or K9NG/K9NG 9600 bps if you prefer).


This requires a note.  My 9600 bps modem in the DSP1232/DSP2232 are
the ONLY 9600 bps modems with an adaptive equalizer on the receive side.
It adapts quickly enough to use it locally on my 9600 bps bulletins
boards and digi/nodes.  These guys are running txd's around 20ms
and the thing adapts quickly enough to easily handle that. I will describe
the thing in detail in another forum.  (Thank goodness K9NG had the
foresight to use a scrambler).  The eye pattern is displayed on the
tuning LED's on the front panel on all my modems (the one with two
data states), and the G3RUH lights two LED's with a BIG black hole
in the middle.  This signifies the opening of the eye with the
adaptive equalizer.  Why did I do this?  UOSAT left the UO22 transmitter
in a mess.  It is badly distorted as the transmitter spectrum has a
well at DC.  The eye patterns in the raw signal are 50% shut.  This
is enough to recover timing but is trouble when the signal gets much below
loud.  This adaptive equalizer opens the eye more than enough for me
to get 5 times the copy of the old modem (not only myself but KA2MOV,
KE7GH, and N6KK report similar results) and at my location it reads
about 15% more than my NB96 (G3RUH by PacComm).  The reason for the
detail about this is that this will be the thing that goes first
when I run out of processor ticks trying to do the dual port 9600's.
If I am required to do this, it will be clearly stated that you must
use decent radios, with reasonably equalized signals out of the
discriminator for it to work well.

Someone put a note on here about doing V.29 through a microphone
jack with a telephone modem chip.  That served as a major impetus
to try it.  If a chip designed to do this on a telephone wire can
do it, I can beat it with the DSP2232, and will attempt to do so.
It would be nice to do 9600 through the mike jack rather than off
the discriminator.

I have completely revamped the WEFAX, and SSTV modems.  WOW!  I
wrote an application for the PC that takes WEFAX DSP2232 output and
displays it.  600 pixels per line, no timing information is encoded
so the picture slides and phasing must be maintained for now with
the help of your finger on cursor keys.  Never mind, the charts and
weather pictures coming out at 16 shades of grey( more than they
encode originally, just convenient) are outstanding!!  I can't wait
for Steve (N6IA) to get his new analog mode done so that I can get
the SSTV stuff on the screen.  The demodulated waveforms on the
oscilloscope look great but we need this mode for it all to hang together.
This will transmit and receive.  The unit is now fully rated at
38400 bps on the serial line to the computer BIDIRECTIONAL.  I have
written a terminal emulator and display software (my first big
assembler programs ever) and it all seems to glue togther.  This is
too exciting.

Bob

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

Date: 9 May 92 18:36:02 GMT
From: swrinde!zaphod.mps.ohio-state.edu!sol.ctr.columbia.edu!spool.mu.edu!agate!rsoft!mindlink![e-mail]
Subject: HamNet?
To: [e-mail]

I'm not too sure what your talking about but I do use the ham radio to send
data, it's very much the same as a BBS.  They call the "normal" BBS's "land
line" BBS's!!

Hope this helps some,

--
=======
Gordon Croft                            "It's a dog eat dog world
                  and I'm wearing milk-bone underwear."
[e-mail]                            -Norm Peterson

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

Date: 9 May 1992 17:36:15 -0700
From: [e-mail]
Subject: In-Reply-To: HamNet?
To: [e-mail]

I don't know about the original poster, but that is what I want to
find more about. A location/file that can give the very novice person
information on TCP-IP.                             ^^^^^^^^^^^^^^^^^^


Thanks for any help

Bob Barnard

> Date: 8 May 92 19:24:32 GMT
> From: [e-mail]
> Subject: HamNet?
> To: [e-mail]
>
> In article <[e-mail]> [e-mail] (Ron) writes:
> >The qusetions a bit vague, but you've found one of the discussion
> >groups (USENET / INTENET /BITNET).  There's also a HAM forum (HAMNET)
>                 ^^^ Internet (typo)
> >on CompuServe, plus numerous other Bulletin boards, plus a system
> >of Bulletin boards run by hams that actually use ham radio to send
> >the messages around rather than phones.
> >
> >-Ron
>
> Unless, of course the original poster ([e-mail]) meant
> computer networks that use Ham radio as part of the transport mechanism
> (e.g., TCP-IP) instead of "networks of people talking about ham radio."
>
>                                       --Rick
>                                         N3JGF
>
> ------------------------------
>

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

Date: 9 May 92 22:48:32 GMT
From: usc!cs.utexas.edu!swrinde!gatech!bloom-beacon!eru.mt.luth.se!lunic!sunic2!mcsun!ieunet!ul.ie![e-mail]
Subject: PacketCluster??
To: [e-mail]

Hello All,

I have recently set up a PacketCluster Node, which is the first in
EI. Things have been running fine, despite a couple of early
problems.
Is there any other PacketCluster SysOp's out there?
I would like to bounce some ideas/problems off them !!!

Mail be at the address below

Thanks


de John
--------------------------
John Barry EI7DNB
[e-mail]

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

Date: Sun, 10 May 1992 05:35:08 GMT
From: usc!sol.ctr.columbia.edu!bronze!ux1.cso.uiuc.edu!news.cso.uiuc.edu!uxa.cso.uiuc.edu![e-mail]
Subject: Ramsey Packet Modem kit ... giving me a carrier tone?
To: [e-mail]

I have put together the Ramsey Packet modem kit, and I am trying to get
it to work with my Standard 2m HT.  I have studied the Standard HT
schematic, and I think that it is pretty similar to the Yaesu, older (?)
ICOM style HT Mic/Spkr input jacks requring something like:

        PTT ------- ~30 Kohm ----------|
                       |
        Xmt ------- .1 uF -------------------------  Mic In

        Rcv ---------------------------------------  Spkr Out
        Gnd ---------------------------------------  Gnd


for connections.  I seem to be able to receive just fine, but for
transmitting, I see the S-meter on the radio jump, but I can't hear any
modulation in a monitoring radio until I fiddle with the "deviation"
resistor in the Packet modem.  Then I get a continuous ~5000 Hz audio
carrier on the monitor radio *except* when packets are going out.
(during which time, I hear a packet modulated signal which sounds good)
The problem is that the modem never drops this carrier, so the HT never
returns to receive mode.

What might be causing this continuous carrier?  And why don't I hear
anything on the monitor radio when the deviation is down?  The transmitting
radio seems to be transmitting something then (at least briefly).

Thanks in advance for any help!

73 de kb8cne (@ka9mnx.il sort of) , Brad Banko

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

Date: (null)
From: (null)
Dr. Funk:

The AEA box has programmable filters and sampling rates.  One of the
modems uses 78000 or so samples per second and the filters will stand
Nyquist rates up to 150 Khz.  If that is fast enough for your applications,
then the answer is yes.  Since the unit is designed for `everyman' doing
modem jobs, the filtering jobs you want done will be for online download
to the DSP box initially.  We are nearing full on the 27C512 and will
soon have to go to the 27C1023.  When we do this, FILTER will be an
operational mode, and you will be given a menu of filters, etc to choose
from.  For the time being, the QLOAD command will allow you to download
these filters to the processor.  I will put a bunch of them on the
AEA BBS if I can get a list.  W3VH is supposed to be getting together a
list that EME'ers will like, I am doing the standard notch filters, narrow
nonringing bandpass filters for morse, etc.  As soon as I get a list of
these things together, I will make a library of these things and post them
with operational instructions on the AEA BBS.  In general, all new modems,
filters, etc. will be available free of charge for download from the AEA
BBS.  Now that I have said all of this, I cannot remember the number of
the BBS!

Bob N4HY
(I work in Princeton)

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

End of Packet-Radio Digest V92 #125
******************************
Date: Mon, 11 May 92 04:30:02 PDT
From: Packet-Radio Mailing List and Newsgroup <[e-mail]>
Errors-To: [e-mail]
Reply-To: [e-mail]
Precedence: Bulk
Subject: Packet-Radio Digest V92 #126
To: packet-radio


Packet-Radio Digest         Mon, 11 May 92       Volume 92 : Issue 126

Today's Topics:
         connecting a Standard HT to a TNC ?
               DSP2232 modems (2 msgs)
                 Info needed
             OS/2 Packet Software needed
                  Subscribe

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: 11 May 92 00:53:19 GMT
From: sdd.hp.com!zaphod.mps.ohio-state.edu!cis.ohio-state.edu!pacific.mps.ohio-state.edu!linac!att!news.cs.indiana.edu!ux1.cso.uiuc.edu!news.cso.uiuc.edu!uxa.cso.uiuc.edu!btbg1194@network.
Subject: connecting a Standard HT to a TNC ?
To: [e-mail]

In article <[e-mail]> [e-mail] (Brad Banko) writes:
>
>
>I suspect that there aren't more articles in rec.radio.amateur.packet
>because most packet guys can get their info off of their local packet
>networks.  I soon hope to count myself among thee.
...
>No!  But seriously.  I have a Ramsey Packet modem kit, and I want to connect
>it to my Standard HT (Heathkit HW-2-M).  The *classic* packet problem.
>I'm a bit nervous about wiring to my HT without being *sure*, but I will
>probably try the "generic" (Old ICOM/Yaesu) approach soon anyway:
>
>     AFSK ---------- 0.1 uF ----------|
>                                      |
>     PTT ----------- 33 Kohm --------------------- Mic In
>
>     SPKR ---------------------------------------- SPKR
>     GND ----------------------------------------- GND
>
>    (TNC) ---------------------------------------- (HT)
>
>I understand that Kenwood HTs are different.  Has anybody actually hooked up
>a Standard HT to a TNC?  Please email me!
>
>Thanks!
>
>73 de kb8cne, Brad Banko
>
>Urbana, Illinois
>[e-mail]
>

The above *does* work with a Standard HT and an AEA PK232... I tested it
today.  The problem seems to be with the Ramsey kit.  I am not very
happy with Ramsey about this.

kb8cne

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

Date: 10 May 92 18:04:30 GMT
From: swrinde!gatech!ukma!widener!beyonet![e-mail]
Subject: DSP2232 modems
To: [e-mail]

    Why does this sound like an advertising con-job to me?
    It looks like a commercial, smells like a commercial,
    feels like a commercial?

    Its informative information though I do admit.
    I guess I have to say keep up the good work...

    Steve
--
 ############### Stephen Urich WB3FTP |"Starlightbeams project ###############
 ##|_|########## Bensalem, PA  USA    |me in Red Blue and Green##|_|##########
 ###############----------------------|Velvetdreams protect me ###############
 ####       #### snark!beyonet!beyo   |when I hit the Screen"  ####       ####
 ##    |_|    ## widener!beyonet!beyo |--Alan Parsons Project  ##    |_|    ##
 ##           ##-----------------------------------------------##           ##
 ####       ####  Packet Radio: WB3FTP@WA3NWL.#EPA.PA.USA.NA   ####       ####
_###############_______________________________________________###############_

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

Date: 11 May 92 07:05:54 GMT
From: mcsun!fuug!funic!nntp.hut.fi!lesti.hut.fi![e-mail]
Subject: DSP2232 modems
To: [e-mail]

In article <[e-mail]> [e-mail] (Bob McGwier) writes:

>This requires a note.  My 9600 bps modem in the DSP1232/DSP2232 are
>the ONLY 9600 bps modems with an adaptive equalizer on the receive side.

 Not really true. The modems in the software for the DSPCARD 3 does include
 a fractional-tap adaptive equalizer for 9600 bps G3RUH by Jarkko, OH2LNS.
 It has been working for about a year now. If anyone is interested in the
 implementation, the sources are freely available e.g. from funic.funet.fi
 /pub/ham/dsp/packet/sources.zip (I haven't checked, but they are probably
 also in tomcat.gsfc.nasa.gov and ucsd.edu). Twin modems for 9600 bps should
 be OK with 56001 since OH2LNS's code does also KISS and HDLC and they consume
 more horsepower than the modem itself.

 73,

 Kaj OH6EH/2

-------------------------------------------------------------------------------
Helsinki University of Technology,      | [e-mail]                     |
Metsahovi Radio Research Station        | !EID RO EVOM                        |
Otakaari 5A, SF-02150 Espoo, Finland    | [e-mail]                 |
--
-------------------------------------------------------------------------------
Helsinki University of Technology,      | [e-mail]                     |
Metsahovi Radio Research Station        | !EID RO EVOM                        |
Otakaari 5A, SF-02150 Espoo, Finland    | [e-mail]                 |

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

Date: 11 May 92 01:18:11 GMT
From: swrinde!zaphod.mps.ohio-state.edu!magnus.acs.ohio-state.edu!usenet.ins.cwru.edu!cleveland.Freenet.Edu![e-mail]
Subject: Info needed
To: [e-mail]

I run a small BBS in Carbondale Illinois on an MSDOS system.  I'd like to know
what type of equipment would be necessary to connect my PC into a packet radio
network, I've seen what appear to be packet radio email addresses on some Use-
net posts I have seen (and listserv lists too) but need more info.  About all
I know is that it's 9600 baud and I think there's internet access too.  I also
know essentially nothing about ham radios, so any info you have would be
appreciated.  Please email rather than posting to the group as I'll be leaving
sometime this week for about a month, and the articles at this site expire after
two weeks.

My apologies if this is a FAQ.

Jerome Grimmer
[e-mail]
[e-mail]
[e-mail]
--
"I'm the Sage!  I know *everything*!//Like, okay.  How, like, does BitNet oper-
ate?\\Operate, schmoperate.  The programmers were drunk out of their minds when
they designed it.  If it wasn't for m00sey intervention it wouldn't work at all

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

Date: Sat, 09 May 92 21:39:56 PDT
From: noiro.acs.uci.edu!ucivax!ofa123!f111.n207.z1.fidonet.org![e-mail]
Subject: OS/2 Packet Software needed
To: [e-mail]

I'm trying to locate some OS/2 packet software.  Can anyone give me some ideas of where to look?  Os/2 Shareware and Fernwood didn't appear to have anything. Perhaps a simple mailbox or such thing..  FTP sites or BBS's appreciated!



--

Chris Epler
Internet: [e-mail]
Compuserve: >internet:[e-mail]

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

Date: 10 May 1992 20:53:45 -0700
From: [e-mail]
Subject: Subscribe
To: [e-mail]

Subscribe   R. Craig Plumlee

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

End of Packet-Radio Digest V92 #126
******************************
Date: Tue, 12 May 92 04:30:02 PDT
From: Packet-Radio Mailing List and Newsgroup <[e-mail]>
Errors-To: [e-mail]
Reply-To: [e-mail]
Precedence: Bulk
Subject: Packet-Radio Digest V92 #127
To: packet-radio


Packet-Radio Digest         Tue, 12 May 92       Volume 92 : Issue 127

Today's Topics:
                DSP2232 modems
                   HamNet?
              IC-32AT for Packet
               VERMONT HAMFEST
          wanted: Kiss EPROM for GLB PK1-L (2 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: 11 May 92 15:01:56 GMT
From: idacrd![e-mail]
Subject: DSP2232 modems
To: [e-mail]



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

Date: 11 May 92 03:20:35 GMT
From: ub.d.umn.edu!cs.umn.edu!kksys.com!edgar!brainiac![e-mail]
Subject: HamNet?
To: [e-mail]

In article <[e-mail]> [e-mail] (Karen Bourque) writes:
>Hi.  I know nothing about Ham radios, I'm inquiring for a
>person who doesn't have access to this net (yet).
>
>He's heard of something like a computer network for Ham
>radio operators.  I've yet to find anything of the sort!
>Anyone out there have any clue as to what he's talking about?
>
>Thanks
>
>Karen

It's not called Hamnet, but maybe he is thinking of the Fidonet Ham Radio
echo.  It is very similar to Usenet, but most of the machines are running
MSDOS, and not Unix machines.

--
Jeffrey R. Comstock
INET  [e-mail]
CW    -. .-. ----- -..

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

Date: 11 May 92 14:46:54 GMT
From: mcsun!sun4nl!tuegate.tue.nl!blade![e-mail]
Subject: IC-32AT for Packet
To: [e-mail]

[e-mail] (Carty Ellis KA2Y) writes:
:
:  What resistors, caps are suggested to use the IC-32AT on Packet.  My
: Alinco DR-110T works just fine, but thinking of a portable set up.
: Thanks.
: KA2Y@WB2PSI.#WNY.NY.USA.NOAM

I am using my IC 32 E (European version) for packet radio for several years
now, and having LOTS of fun with it as a ""fixed"" station... Just remember
to switch off the power saver...

To connect my TNC2c to the transceiver, I use this little scheme:

        || .1 uF
tx-audio>---||--------+----< micr jack
        ||        |
              |
     ptt>-v^v^v^------+
     5-15 kOhm
rx-audio>------------------< speaker jack
     gnd>------------------< gnd

I also have made some "tabs" in the transceiver to connect a VE3DNR/4k8
modem, though I haven't had time yet to try them... If there's someone
interested I'll post these things too...


      Best regards, Ramon
--
-------------------------------------------------------------------------------
Ramon Kolb    Internet: [e-mail]
PA3EUG        AMPRNET : [e-mail]; [e-mail]
          BBS     : PA3EUG @ PI8HRL.#LB.NLD.EU.Earth
This mail was posted from The University of Technology, Eindhoven, NL

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

Date: 11 May 1992 04:48:00 -0700
From: [e-mail]
Subject: VERMONT HAMFEST
To: [e-mail]

Date sent:  11-MAY-1992 07:47:22
>                                 Presenting the
>                        NORTHERN VERMONT SUMMER HAMFEST
>                                      and
>                           Computer Technology Fair
>                         Saturday,  June 6,  8am - 3pm
>
>  INDOOR AND OUTDOOR FLEA MARKET                  FORUMS AND MEETINGS
>
>Big indoor facility - No rainouts!                    ARRL Forum
>
>     Flea Market spaces FREE!                        Packet Radio
>
>        Tables available                           Weather Spotters
>
>     Retail Sales / Dealers                   FIRST EVER! VT DXers Forum
>
>        CONVENIENTLY LOCATED                       DEMONSTRATIONS
>
>    Nearby Restaurants and Motels                   Packet Radio
>
>     Across from University Mall                 Amateur Television
>
>    Drop off the family at the mall               Antenna Building
>
>   Spend the day buying ham goodies!          Latest Computer Software
>
>
>         Amateur VE Exams at 2 PM - All Classes of Licenses Offered
>
>          ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>          +             Conveniently located at the                +
>          +         South Burlington Middle School Campus          +
>          +      Dorset Street, 1 mile South of Williston Road     +
>          +  From I-89, exit 14-E, immediate right onto Dorset St. +
>          ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
>      Admission: only $3, kids under 18, FREE.  Flea market spaces, FREE
>
>      ++++++++++++++++++++                      ++++++++++++++++++++++++
>      + Hamfest Talk-In: +                      + For more information +
>      + WA1WLM Repeaters +        food!         + Flea Market:         +
>      +  146.25/146.85   +      beverages!      + N1DMP   802-893-6458 +
>      +  147.45/146.85   +      ice cream!      + VE Exams:            +
>      + 444.025/449.025  +     book sales!      + WB2JSJ  802-879-6589 +
>      ++++++++++++++++++++                      ++++++++++++++++++++++++
>Date: Wed, 13 May 92 04:30:03 PDT
From: Packet-Radio Mailing List and Newsgroup <[e-mail]>
Errors-To: [e-mail]
Reply-To: [e-mail]
Precedence: Bulk
Subject: Packet-Radio Digest V92 #128
To: packet-radio


Packet-Radio Digest         Wed, 13 May 92       Volume 92 : Issue 128

Today's Topics:
           [FWD] Internet<>Packet Gateways
                DSP2232 modems
       Max2.01wb, Squish1.01, AreaFix 1.30 (& BATPOWER)
               Mfj-1270B Host Mode Help
           Modulation of Alinco Data Radio
              TAPR's 9600 Modem

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 May 1992 13:57:16 -0700
From: [e-mail]
Subject: [FWD] Internet<>Packet Gateways
To: [e-mail]

Someone on the packet "forum" asked a while back
about Internet to Packet gateways.
K9HI, Phill advises:
>From: [e-mail] (Phil Temples)
>
>There are currently several Internet <> packet radio e-mail gateways in
>operation in the U.S.
>
>Here is what I know:
>
>  The W2XO gateway in Pittsburgh, PA.  It is bi-directional; however, an
>internet addressee must be "registered" with Jim.  In other words the
>ax.25 sender cannot simply send to anyone on internet; only those users
>who have made prior arrangments.  Mail coming in for ax.25 users must,
>of course, be screened for content before making the hop over to amateur
>packet radio.  Jim can be reached at: [e-mail] (Jim Durham).
>
>  There is also the KA2QHD gateway in New Jersey.  Is is, I believe,
>uni-directional (packet->internet).  Again, an internet user must be
>registered with the sysop.  Contact John at:
>[e-mail] (John Decatur).
>
>  Finally, there is a new gateway in the Phoeniz, AZ area run by WB7TPY.
>It is bi-directional to my knowledge.  (Actually, I would describe it as
>more "tri-directional"; it seems to be tightly coupled to Fidonet via a
>gateway as well.)  For more information, contact David at:
>[e-mail] (David Dodell).
>
>All of these gateways use slightly different syntax and procedures.  You
>would be well-advised to contact the sysops before sending any e-mail
>messages.  I make no guarantee that my information is one hundred per
>cent correct.  And, your mileage may vary.  Good luck.
>
>-Phil, K9HI
>
>~~~
>
>"If they had money, they'd be Republicans."  -- Dennis Miller, commenting
>on why most of the checkbouncers in the Congress are Democrats
>
>Phil Temples, Software Engineer         Optronics, an Intergraph Division
>7 Stuart Road, Chelmsford  MA 01824 USA  [phone]    [e-mail]
>

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

Date: 12 May 92 20:00:10 GMT
From: idacrd![e-mail]
Subject: DSP2232 modems
To: [e-mail]



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

Date: 8 May 92 20:05:09 GMT
From: munnari.oz.au!comp.vuw.ac.nz!waikato.ac.nz!aukuni.ac.nz!mercury!nacjack![e-mail]
Subject: Max2.01wb, Squish1.01, AreaFix 1.30 (& BATPOWER)
To: [e-mail]

In a message of <May 07 10:49> Murray Thessman (3:771/160@fidonet) writes:

 MT> ** BATPOWER ** I have decided to pickup BATPOWER on trial. Ii is
 MT> on Batch programming. If the flow is small & content is good I
 MT> will to get it. If others are interested please drop my a msg.

Batpower has a weekly volume of about 70 messages.  I can't make any comment
on the content.

Greg :-)




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

Date: Mon, 11 May 1992 21:28:00
From: usc!cs.utexas.edu!convex!seas.smu.edu!utacfd.uta.edu!trsvax!rwsys!ocitor![e-mail]
Subject: Mfj-1270B Host Mode Help
To: [e-mail]

Does anyone know how or if the MFJ-1270B tnc can be put into the host
mode. I am trying to run AA4RE's bbs program. I keep getting crit errors
like the tnc is not responding to the bb.exe file. I know my parameters
are set right because while the program is loading I am copying the
local packet transmissions. I am running this program on an IBM
compatible xt. I can run the tnc with my land line terminal program with
the same settings and it does fine. Can anyone help me with this. Any
help would be appreciated. Thanks and 73, Mark N5ORU.
 * Origin: Com Port 1 - DFW Amateur Radio BBS [phone] (1:124/7009)

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

Date: 12 May 1992 12:17:36 -0700
From: [e-mail]
Subject: Modulation of Alinco Data Radio
To: [e-mail]

I was wondering if the Alinco data radio's modulation occurs
inside of a PLL (like many voice rigs), or if it's done
outside the loop.  I'm curious because I know that doing it
inside the loop can cause problems when trying to run at
9600 baud.   Can anyone out there relate some experiences
using this rig at 9600 baud?

-- Dan Larner, WV9Z
[e-mail]

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

Date: 11 May 92 9:13:26 GMT
From: munnari.oz.au!comp.vuw.ac.nz!waikato.ac.nz!aukuni.ac.nz!mercury!nacjack![e-mail]
Subject: TAPR's 9600 Modem
To: [e-mail]

Where exactly can I purchase the TAPR 9600 modem? Do they take VISA?

It's just that I want to work in TCP/IP and 1200 is far to slow! I have a
Kenwood TM-241A - will it work with the modem?

---------------------------------------------------------------------------
And Noah Spaketh unto his children: "Scattered showers my arse!"

FIDONET: Richard Vowles 3:772/110.0         USENET: [e-mail]
Packet Radio: ZL1UTF@ZL1AB.#11.AKL.NZL.OC   The Demi-Monde: 199:310/1

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

Date: (null)
From: (null)
Hi Kaj:

That is great news.  The story on the HDLC and KISS cannot possibly be right.
I agree that they are pigs and use a lot of ticks, but they cannot consume more
total ticks than the 9600 bps modem.  You might mean that their processing can
be deferred since they are the foreground task and that while they are running
they use most of the processor ticks but it should be clear that for most of
the time they are sitting idle waiting for the `HDLC has arrived' flag to go
up and then KISS only gets executed when HDLC says it received a valid frame.
The 9600 bps modem must be executed each and every sample time and can be deferred
only with great difficulty.

I am sorry I did not know about your equalizer modem.

Congratulations.

Bob


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

End of Packet-Radio Digest V92 #128
******************************
Date: Thu, 14 May 92 04:30:04 PDT
From: Packet-Radio Mailing List and Newsgroup <[e-mail]>
Errors-To: [e-mail]
Reply-To: [e-mail]
Precedence: Bulk
Subject: Packet-Radio Digest V92 #129
To: packet-radio


Packet-Radio Digest         Thu, 14 May 92       Volume 92 : Issue 129

Today's Topics:
         Any TCP/IPers in Chattanooga/Lookout Mtn TN?
                DSP2232 modems
              TAPR's 9600 Modem
          TCP/IP connectivity outside packet
             TS-690 to PK-232 connection
          WNOS question regarding SLIP, more

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 May 92 19:52:47 GMT
From: mjbtn!knuth!knuth![e-mail]
Subject: Any TCP/IPers in Chattanooga/Lookout Mtn TN?
To: [e-mail]

Hello!  Myself and a few others are looking for persons in the
Chattanooga and Lookout Mtn TN/GA area who are doing TCP/IP now, plan to
in the future, or just plain ol' curious about it.

We are aware of the WQ4B/LOM switch atop Lookout Mtn. on 145.09, and
that it has a TCP/IP port on it, but we know nothing more about it.  We
would like to learn more about this switch, i.e., the TCP/IP frequencies
and configuration, etc.  Attempts to contact WQ4B via packet or the
mails or Internet have been unsuccessful so far.  Anyone else associated
or acquainted with this effort is invited to contact us or let us know
how we can call/write/E-mail you/them.

We manage a club station here at Middle TN State University (W4EFQ)
which is growing and moving towards TCP/IP implementation, full Internet
capabilities, and other such endeavors.  We are very close with Dave,
WB4LHO, and his efforts to run and enhance the TCP/IP switch atop Short
Mountain (McMinnville/Warren Co.) TN, which serves into Nashville and
reaches WQ4B's switch on Lookout Mtn.  Information coming to us about
the efforts of the GRAPES group in Atlanta and their 56K bps work have
captured our interest and working with anyone, especially WQ4B/LOM or
any group working out of that area would be a major step in linking a
backbone up towards Nashville.

If you or anyone you know of has *any* information you could offer,
please E-mail us at the following addresses:

Mark N4XHX: N4XHX@AB4ZB.#MIDTN.TN.USA packet,
        [e-mail] OR [e-mail] <Internet>,
        MTSU Computer Science, PO Box 48, Murfreesboro TN 37132,
        615-893-0098 <work>.

John KD4EAI:KD4EAI@AB4ZB.#MIDTN.TN.USA packet,
        [e-mail] OR [e-mail] <Internet>,
        MTSU Ctr. for Remote Sensing, POB 135, Murfreesboro 37132,
        615-898-5561 <work>.

Dave WB4LHO:WB4LHO@AB4ZB.#MIDTN.TN.USA packet,
        [e-mail] <Internet>

Kelly KC4RDJ:KC4RDJ@AB4ZB.#MIDTN.TN.USA packet,
        [e-mail] <Internet>

Club Station W4EFQ -- W4EFQ@AB4ZB.#MIDTN.TN.USA or
              W4EFQ@KC4RDJ.#MIDTN.TN.USA packet

All of us also subscribe to a list '[e-mail]' for
discussions relating to packet in Middle TN and the Tennessee Valley.
This list is somewhat quiescent (sp?) but we are all there.  (Any pun is
somewhat unintentional.)  We would appreciate your e-mail replies rather
than reposts to the list, unless of course your message benefits us all!

Thanks for your help!  73s, CUL
--
John N Schmidt KD4EAI, Lab Director | 615-898-5561 M-F 1300-2230Z <7-4:30>
Middle Tennessee State University   | 615-898-5538 or 896-2871 FAX 24H
1500 Greenland Drive, PO Box 135    | [e-mail] <Internet Address>
Murfreesboro, TN  37132-0135 USA    | MTSU Center for Remote Sensing/GIS

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

Date: Wed, 13 May 92 12:45:37 GMT
From: tijc02![e-mail]
Subject: DSP2232 modems
To: [e-mail]



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

Date: 13 May 92 14:30:12 GMT
From: ulowell!tegra![e-mail]
Subject: TAPR's 9600 Modem
To: [e-mail]

In article <[e-mail]> [e-mail] (Richard Vowles) writes:

   Where exactly can I purchase the TAPR 9600 modem? Do they take VISA?

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

Date: 13 May 92 17:14:09 GMT
From: usc!zaphod.mps.ohio-state.edu!think.com!mintaka.lcs.mit.edu!bloom-beacon!eru.mt.luth.se!lunic!sunic2!mcsun!uknet!mucs!p4.cs.man.ac.uk![e-mail]
Subject: TCP/IP connectivity outside packet
To: [e-mail]

Recently it came to my attention that gb7tcp.ampr.org is recognised by our
Internet name server and it gives the address as 44.131.whatever.  Connection
attempts fail (as expected) but it seems odd that the name server understands
them if there isn't a gateway available.  So my question is this:  is it at
all possible to connect to such a TCP/IP station from the Internet?  If so,
what are the licensing implications of this, especially from the point of view
of a non-licensee such as myself?

I look forward to your replies.

--
[  Ian Chard, Computer Science I  |  Life is pretty good at the moment.       ]
[  Manchester University          |  A no-code HF license?... well, that      ]
[  [e-mail]         |  would make it just about perfect.        ]

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

Date: 13 May 1992 16:13:30 -0700
From: [e-mail]
Subject: TS-690 to PK-232 connection
To: [e-mail]

Hello,

This is in response to a post a couple of weeks ago on connecting a
TS-690 to a PK-232.  This is the hook-up that I use.  It works well
for all the data modes.  Page 22 of the Kenwood manual details the
ACC2 connections and the PK-232 connections are found in its manual.

     TS-690                               PK-232
      ACC2

       2                                   J7-4   FSK keying
       3                                   J4-1   RX audio
       4                                   J4-4   Audio ground
       8                                   J7-2   FSK ground
       9                                   J4-5   PTT
      11                                   J4-2   TX audio

Notes:

   1. On the PK-232 J4 is the Radio 1 port and J6 is the Radio 2 port.
      J4 and J6 can be used interchangeably.

   2. I use the FSK for most of my digital communications.  It allows
      me to use the narrow filter for digital.  For an explaination,
      see page 38 in the Kenwood manual.  I hooked up the TX audio
      in case I ever wanted to do AFSK.

******** WARNING ******* WARNING ******* WARNING ******* WARNING ********

    YOU MUST!!!!! DISCONNECT THE PK-232 BEFORE USING SSB!!!!!

    If you do use SSB with the TNC hooked-up, your SSB will be
    horribly distorted.  I talked with a Kenwood technician
    about this, and the only solution so far is to disconnect
    the TNC.

******** WARNING ******* WARNING ******** WARNING ******* WARNING ********

  DISCLAIMER:  Anything you try with your TNC and your radios is your
           responsibility.

Let me know how things work out.

73, Erich   KA6AMD

AX.25:  KA6AMD @ WA6YBN.#SOCA.CA.USA.NA
Internet: [e-mail]

"I know the pen is mightier than the sword, its just that hacking about
with the sword is so much more satifying."

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

Date: Thu, 14 May 1992 03:37:33 GMT
From: usc!sol.ctr.columbia.edu!137.148.5.51![e-mail]
Subject: WNOS question regarding SLIP, more
To: [e-mail]

Hello netters:

I am not a radio person, though I respect those who use it and perhaps one
day because it has many interesting possibilities!

I do have packet and SLIP connectivity to the internet and the Ka9q/NOS
programs are outstanding.

Recently I picked up the latest and not latest wnos3.x variants.  I compiled
these programs using Borland C++ version 2.0.  For some reason it would NOT
compile under Borland C++ version 3.0.  I had all the SLIP code but the
attach asy command is not recognized.  Compiled WNOS will accept an attach
packet command, but I would like the SLIP ability to be usable.  I have had
other problems, too.

The screen is very cluttered and the text will not scroll properly, thus
filling the screen with text.

I have some kind of router problem.  the program asks for arfconv.exe but I
cannot find this file on Archie or several of the NOS sites.  It is
frustrating.

I love this software and desire to use it or some variant of ka9q/NOS that
does everything WNOS does.  But the interface in WNOS is superior and I want
to use it all the time.  Can anyone help?  Is there a pre-compiled version
without the radio packet code and the slip code that allows an attach asy
command?  Is there an ftp site and files I can use?  Can someone compile a
version with SLIP and allow ftp or email in uuencoded format?

Please help, and thanks for anything anyone can do for me 8-)

Please reply to this address: [e-mail].  My current node is
a test site and not up all the time, or even most of the time.

Thanks again!
Joe

| Joe Rosenfeld  [e-mail]  [e-mail]
| "We look for things ... to make us go!"--Pack-led Traders.

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

Date: (null)
From: (null)
   It's just that I want to work in TCP/IP and 1200 is far to slow! I have a
   Kenwood TM-241A - will it work with the modem?

To work with any radio you have to tap into the "guts".  True FM
crystal radios are usually reccomended but with fiddling other
synthesized radios have been made to work.  I don't know about that
one in particular.

good luck, jv


"The death of God left the angels in a strange position."
 _____
|     | Johnathan Vail     [e-mail]     [phone]
|Tegra| [e-mail]    N1DXG@448.625-(WorldNet)
 -----  MEMBER: League for Programming Freedom ([e-mail])

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

Date: (null)
From: (null)
FB on the DSP232 work, Bob. You are doing some interesting work there and
I'm happy to listen to your 'compensation.' And it makes an interesting
story as well.

73, Ed WX4S

Ed Ingraham
Siemens Industrial Automation, Inc.        [phone] voice
3000 Bill Garland Road                     [phone] fax
P. O. Box 1255                             [e-mail]
Johnson City, Tennessee 37605-1255

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

End of Packet-Radio Digest V92 #129
******************************
Date: Fri, 15 May 92 04:30:04 PDT
From: Packet-Radio Mailing List and Newsgroup <[e-mail]>
Errors-To: [e-mail]
Reply-To: [e-mail]
Precedence: Bulk
Subject: Packet-Radio Digest V92 #130
To: packet-radio


Packet-Radio Digest         Fri, 15 May 92       Volume 92 : Issue 130

Today's Topics:
        Non FAQ packet questions / help please
         NOS for Unix? Fast radio modems? Gatewaying?
           wanted: Kiss EPROM for GLB PK1-L

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: Thu, 14 May 1992 13:37:09 GMT
From: usc!sol.ctr.columbia.edu!news.unomaha.edu!odin![e-mail]
Subject: Non FAQ packet questions / help please
To: [e-mail]

[e-mail] (Mike LaPierre) writes:

>Hi,

>I am interested in getting into packet and so far all the info I've
>been able to find here on the net about packet is VERY general and
>VERY non-technical. I have some questions that hopefully someone
>can answer for me.

Speaking on behalf of the FAQ Coordinators, Mike's complaints are valid.
We would very much like additional technical information and pointers to
other references to "beef up" the FAQ.  In addition to answering Mike's
questions, could those on the net "in the know" help make the FAQ more
useful by CC'ing the answers to [e-mail]?

We are working on merging the submissions of the past 6 months or so,
and should have a new version out very soon now.  We would very much
like to add your name to the acknowledgements list.

Welcome to the newsgroup and the net, Mike!  I hope that we can offer
you the technical insight that you seek.

73, Paul W. Schleck, KD3FU

[e-mail]

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

Date: Thu, 14 May 92 16:05:54 GMT
From: usc!zaphod.mps.ohio-state.edu!magnus.acs.ohio-state.edu!usenet.ins.cwru.edu!slc8![e-mail]
Subject: NOS for Unix? Fast radio modems? Gatewaying?
To: [e-mail]

Several questions for the net...

Someone let me know if there is a better place to discuss the following
topics...


Does anyone know of any NOS packages that have been put together for
Unix (xenix, ultrix, etc...)??

What are the fastest speed radio modems that are available?

How feasible is it to "gateway" between an Ethernet and a TCP/IP'ish radio
network... neglect for the moment the FCC's restrictions regarding auto
forwarding via the airwaves... Say that this was going to be done on a
commercial frequency...

If you were going to create a "wan" using radio, would you use direct
links, that would be analogous to leased phone lines, or would you create
a TCP/IP network with packet radio, that would be more like a BIG Ethernet?


Why am I asking??? Several sites in this area are considering methods of
circumventing the phone co in setting up a WAN. One of the proposed methods
would be to get a commercial frequency, and use packet radio. The technology
would be similar to Amateur Packet, but would not have some of the same
restrictions.

In the long run, paying for all of this would probably be less expensive
than paying to use phone lines, especially if things could be done between
billing areas.

There are several problems that we know that we have to consider... like:

"How do you keep people from just adding themselves to the net?"
"How can you expect this to be anywhere near private?"
"How can you keeps this secure?"
etc...

Any and all thoughts would be appreciated. I can post a summary if people
email, but, I would guess that it wouldn't hurt to see some of the answers
just posted to the whole net, rather than emailed just to me.

Later.
Dan

--
Dan Brown
[e-mail]

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

Date: 14 May 92 22:06:27 GMT
From: swrinde!zaphod.mps.ohio-state.edu!ub!acsu.buffalo.edu![e-mail]
Subject: wanted: Kiss EPROM for GLB PK1-L
To: [e-mail]

In article <[e-mail]>, [e-mail] (Dave Horsfall) writes:
> As of a couple of months ago, GLB were denying it ever existed, and had
> no plans to produce one.  Perhaps someone has written one?  I'd be interested!
> It could make a fine KISS modem - it's certainly hopeless for its intended
> application, and I believe it only supports V1.0 of AX.25 as well, despite
> what GLB may claim.

A few of us were working on this a while back but got side-tracked and never
resumed. The big problem is that the PK1-L has no UART. All communication
(both on the serial and radio side) is done by polling the bits and timing
is done by counting the cycles in your code! So, needless to say, programming
is tedious and we sort of lost interest.

Hmm... in fact, there was something about KISS that made "real" KISS
impossible on the PK1-L. I forget what that feature is but any KISS that
would be made for it would be lacking. Perhaps it was the back-off timer?
I don't remember...

Devon

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

Date: 14 May 1992 11:42:34 -0700
From: [e-mail]
To: [e-mail]

References Faunt, N6TQS, 415-688-8269)
p
Subject : TAPR's 9600 Modem

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

End of Packet-Radio Digest V92 #130
******************************
Date: Sat, 16 May 92 04:30:03 PDT
From: Packet-Radio Mailing List and Newsgroup <[e-mail]>
Errors-To: [e-mail]
Reply-To: [e-mail]
Precedence: Bulk
Subject: Packet-Radio Digest V92 #131
To: packet-radio


Packet-Radio Digest         Sat, 16 May 92       Volume 92 : Issue 131

Today's Topics:
               DSP2232 modems (2 msgs)
                 NOS for Unix
          Procomm modem program mods for packet use

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 May 92 18:53:41 GMT
From: orca!javelin.sim.es.com!nu.sim.es.com![e-mail]
Subject: DSP2232 modems
To: [e-mail]

Is the DSP2232 fast enough to decode the HRPT weather  mode?

If it is is anybody working on it?


73,  Randy N7SFI

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

Date: 15 May 92 19:54:29 GMT
From: orca!javelin.sim.es.com!nu.sim.es.com![e-mail]
Subject: DSP2232 modems
To: [e-mail]

Is the cpu/DSP in the DSP2232 fast enough to decode the HRPT mode of some of
the weather sats?

If so,  is anyone working on it?

73, Randy N7SFI

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

Date: 15 May 1992 15:33:48 -0700
From: [e-mail]
Subject: NOS for Unix
To: [e-mail]

Someone asking about NOS for Unix I think....there is a version of KA9Q NOS for
Unix floating about.....for the version of Unix which I use (Linux - a free
system V compatible Unix which runs X, etc. - just thought I'd give it a plug!)
you can find it on places like tsx-11.mit.edu (in the subdirectories of
/pub/os/linux) and puffin.doc.ic.ac.uk.  Hope this helps,

73 de John G0NSI @ GB7DDX   [44.131.5.85]   [e-mail]

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

Date: 16 May 92 03:53:30 GMT
From: swrinde!zaphod.mps.ohio-state.edu!cis.ohio-state.edu!pacific.mps.ohio-state.edu!linac!att!cbfsb!cbnewsb.cb.att.com![e-mail]
Subject: Procomm modem program mods for packet use
To: [e-mail]

copied from packet:
  Msg# TSF   Size #Rd  Date  Time  Arrived Seq #      Msg ID      Route
   816 BF    1775   3 12-May 0423z 12-May (003793 - 8056_N2IVL  ) []
  N2LSJ  ==>  ALL@ALLBBS
  "Procomm Modification For Packet."

Greetings packet users with procomm.  Here is a really neat
mod that you can perform on your Procomm Communications Program.
This mod will allow you to use your modem dialing directory as
a connect directory, which will allow you to use quick keys when
connecting to your favorite packet station.

Go into the modem setup screen and delete the modem init. string.
Next, delete the modem dial cmd and replace it with ^C.
Then delete the dial cmd suffix and replace it with ^M.
That is ^C   and   ^M   there are no periods after the command.
Once that is complete you hit ESC and choose save to disk as
the option.

Finally, go to the modem dialing directory by using ALT/D and
start revising the directory.  Where it calls for the name of the
pbbs just give it a name that is suitable for you.  When it asks for
the telephone number, simply put the letter C [space] callsign and
ssid number.  Ex: C N2XXX-4 and then the hard part is over.  The
is to put E71 and choose if you want echo or not.

This mods works with Procomm ver.2.4.2 and Procomm Plus however, it
should work for modem programs like Telix and other alike.
73 de Jim ..._._
========================================================================
Note: I haven't tried or veriied this, proceed at your own risk.  WA2ISE

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

End of Packet-Radio Digest V92 #131
******************************
Date: Sun, 17 May 92 04:30:03 PDT
From: Packet-Radio Mailing List and Newsgroup <[e-mail]>
Errors-To: [e-mail]
Reply-To: [e-mail]
Precedence: Bulk
Subject: Packet-Radio Digest V92 #132
To: packet-radio


Packet-Radio Digest         Sun, 17 May 92       Volume 92 : Issue 132

Today's Topics:
        Non FAQ packet questions / help please
              Nos for Unix, ...
                 unsubscribe

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 May 92 14:06:09 GMT
From: swrinde!mips!think.com!rpi!gatech!news.byu.edu!news.mtholyoke.edu!nic.umass.edu!hamp.hampshire.edu![e-mail]
Subject: Non FAQ packet questions / help please
To: [e-mail]

Hi Mike,

I'm not a real expert, but I've played a little with packet on VHF and
HF. I'll take a cut at some of your questions...

>1) I keep seeing references to packet modems while talking about
>   TNC's. Is a separate modem needed in addition to a TNC?

Logically the modem and tnc are separate units. Most tnc products
include a modem for 1200 baud and lower speeds. For higher speeds
modems are usually add-ons.  There are a couple of software-based
systems, Baycom and Poor Man's Packet for IBM and Digicom for
Commodore, that require only a modem and do the tnc job in software.

>2) What exactly does the TNC do and what are the different stages
>   of processing.

The main job of the TNC is the OSI data-link level, taking a stream of
bits and assembling them into packets or vice-versa. The modem takes
care of the OSI physical level.  Most TNCs do only this when in KISS
(Keep it simple..) mode, but by default do quite a bit of additional
work, so that a simple dumb terminal program is adequate to handle
communications and control packet functions -- you normally  don't see
the headers of packets or handshaking packets or packets not  addressed
to you.

>3) I want a small portable setup and I want to be able to do 9600
>   baud and be able to swap the ROMS if necessary. What TNC's are
>   are available that provide these capabilities? (I want the newest,
>   best etc. but small/portable).

Here I can't help you -- I have used the Kantronics KAM, it's not big, but
I know there are much more compact units that are better  matches to
handheld transceivers.

>4) Where can I find info on LEOS satellites?
>5) What satellites are available on VHF/UHF?
>6) How can I find out about store/forward BBS satellite systems?
>7) Do you need a special TNC or equipment to access these satellites?
>   (I am not interested in HF systems, only VHF and UHF)

For the satellite questions see the ARRL Satellite Experimenters
Handbook. There is not a lot on digital modes, but there is some basic
info. This is not something I have experience with (yet -- I have plans!)
but my sense is that there are no special techniques used, basically
these are orbiting bulletin board systems.

For up to date info on availability of satellites and tracking data, bulletins
are frequently posted on rec.radio.amateur.misc, and also on local packet
bulletin board systems.
If you are interested in serious non-amateur use of LEOSatellites you
might want to contact Volunteers for International Technical Assistance
(VITA) in Washington.  They are very involved in promotion of low-orbit
store and forward communications for Third-World development projects.
They can be contacted at [e-mail].

73 de Al Woodhull   N1AW
[e-mail]
School of Natural Science, Hampshire College, Amherst, MA

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

Date: 16 May 1992 08:35:36 -0700
From: [e-mail]
Subject: Nos for Unix, ...
To: [e-mail]

Hi,

I don t believe there are any commercial frequencies above 30 Mhz and below
900 Mhz for the purpose u envision. These allocations are for Land-Mobile,
and using them for communicating between "Bases" is not correct. Sure, it
happens, but its not going to be endorsed by the FCC.

Why is that important ? Well it has allot of implications as to the radio
system design. How far a radio system can work, is directly related to the
size of the antenna. A large antenna in this spectrum, is relatively simple,
and can be made omni directional. A large antenna at frequencies above this
spectrum is probably going to be unidirectional, a "beam" in other words.

There s a possibility of doing "Point-MultiPoint" in the spectrum between
900 and about 1800 Mhz, but recent international allocation stuff is making
that a doubtful proposition. I think Motorola is doing something like this,
with T1 data rates, but don t know the details. Basically the subscriber
puts up a beam pointed at the T1 switch station, which is omnidirectional.
This is not exactly what u are looking for. Right? Since instead of the
phone company, u got Motorola to pay. What s the diff? I m not even sure
they use IP protocoll.

So, these things basically constrain ur system to a point-point scheme, if
ur thinking of doing it urselves. The idea of a big Ethernet just is not
practical on commercial radio , executed by the users alone.

WAN is an imprecise term. With the great differences in ranges of in-
dividual radio circuits, u really can t define WAN from the "Ethernet/
Unix" user point of view, as everybody in one building. On radio a
LAN is any channel where ALL the users can communicate directly, with no
other switch equipment inbetween. A WAN then would be any network where
the data has to tansvers a switch, and usually end up on another radio
channel, some distance away. Lan s can thus very from ones surrounding
neighborhood, to a Metropolitan area coverage system, to a mountain top
based repeater supported system that covers several states. The real
guiding prinicipal about selecting a LAN size is how much thruput is needed.
In the metropolitan areas LAN s need to be small, on the order of 10 miles
diameter. From ur note, it seems u are interested in linking wire line
LAN s together by Radio, not having the LAN on radio. In which case, the
Point-point scheme has no real problems. If however u wish to have the
LAN on radio as well, then the commercial spectrum is really not well
suited. Oops, the second use of WAN in this paragraph should read LAN .

73, Don [e-mail]

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

Date: 16 May 1992 10:53:58 -0700
From: [e-mail]
Subject: unsubscribe
To: [e-mail]

>Return-Path: <[e-mail]>
>Date: Sat, 16 May 92 10:36:37 -0700
>To: [e-mail]
>Subject: Re: your LISTSERV request "list"

>Per your request
>        "list"
>'[e-mail]' is not subscribed to any mailing lists.

Right, why am I still getting it then! Can someone PLEASE unsubscribe me.

Thankyou,
--
Michael
Internet [e-mail]
AMPRnet [e-mail]   [44.4.1.247]

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

End of Packet-Radio Digest V92 #132
******************************
Date: Mon, 18 May 92 04:30:02 PDT
From: Packet-Radio Mailing List and Newsgroup <[e-mail]>
Errors-To: [e-mail]
Reply-To: [e-mail]
Precedence: Bulk
Subject: Packet-Radio Digest V92 #133
To: packet-radio


Packet-Radio Digest         Mon, 18 May 92       Volume 92 : Issue 133

Today's Topics:
             tapr 1.1.8 uploaded

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: 18 May 1992 01:13:31 -0700
From: [e-mail]
Subject: tapr 1.1.8 uploaded
To: [e-mail]

The latest version for tnc2 1.1.8 just uploaded to ucsd.edu
in hamradio/packet/tcpip/incoming
It was copied from satel via SV1LH.
73 de George SV1BDS

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

End of Packet-Radio Digest V92 #133
******************************
Date: Tue, 19 May 92 04:30:02 PDT
From: Packet-Radio Mailing List and Newsgroup <[e-mail]>
Errors-To: [e-mail]
Reply-To: [e-mail]
Precedence: Bulk
Subject: Packet-Radio Digest V92 #134
To: packet-radio


Packet-Radio Digest         Tue, 19 May 92       Volume 92 : Issue 134

Today's Topics:
             2400 bps modulation
             arp publish (2 msgs)
               Baymod-9/Baycom
             CELLNET info needed
              Digicom Wanted - third try
                   HamNet?
                 NOS
                 NOS for Unix

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: Mon, 18 May 1992 08:05:45 GMT
From: munnari.oz.au!ipso![e-mail]
Subject: 2400 bps modulation
To: [e-mail]

What is the modulation scheme used for 2400bps packet?  Since Kantronics,
MFJ etc all have compatible hardware, I would guess it's a common chip
such as used for V.22bis?  My KPC-2400 just has a Kantronics part ID on
the modem chip.

Speaking of Kantronics, what is the microprocessor used?  Looks like
a "6303" or something - I've never heard of it, but I believe it has
a built-in UART etc, and possibly other "smarts" too.

--
Dave Horsfall (VK2KFU)         VK2KFU @ VK2RWI.NSW.AUS.OC
[e-mail]                  ...munnari!ips.OZ.AU!dave
 "Difference between a virus and Windows?  A virus never fails" - R.Mulder

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

Date: 18 May 92 17:16:49 GMT
From: usc!sol.ctr.columbia.edu!spool.mu.edu!agate!remarque.berkeley.edu![e-mail]
Subject: arp publish
To: [e-mail]

   I need pointers to docs or experts on arp publish.

     Tim

--
Internet: [e-mail]               FidoNet:  Tim Pozar @ 1:125/555
UUCP:     ...!uunet!kumr.lns.com!pozar
Snail:    Tim Pozar / KKSF / 77 Maiden Lane / San Francisco CA 94108 / USA
Voice:    [phone]

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

Date: Mon, 18 May 1992 21:31:48 GMT
From: usc!cs.utexas.edu!tamsun.tamu.edu!cs.tamu.edu![e-mail]
Subject: arp publish
To: [e-mail]

ARP publish is also known as proxy ARP.  For example, I have 3 boxes on an
Ethernet: AT, SX, and DX.  AT has two radios on it.  So that other users
don't need a specific route to get to SX and DX, AT has two arp publish
entries:

arp publish sx.wb5bbw.ampr.org ax25 wb5bbw-8
arp publish dx.wb5bbw.ampr.org ax25 wb5bbw-8

Now, when soneone ARP requests sx.wb5bbw.ampr.org, my AT blasts out an ARP
reply with AT's AX.25 callsign.  When AT gets a packet for SX or DX, he
sends it over the Ethernet link.  Neat, hah?
  Unfortunatley, ARP proxt canbe misuses.  RIP ought to help out, but it is
a quick and dirty fix.  In entering this tome, I realize that if someone
tries to get to SX or DX from the other radio, it'll not work.  But there's
not too many folks over there anyway..... 8-}

73, Kurt

--
Kurt Freiberger, wb5bbw   [e-mail]   409/847-8607  fax:[phone]
Dept. of Computer Science, Texas A&M University      DoD #264: BMW R80/7 pilot
"We preserve our freedom using three boxes: ballot, jury, and cartridge."
      *** Not an official document of Texas A&M University ***

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

Date: Mon, 18 May 92 16:22:58 GMT
From: usc!sol.ctr.columbia.edu!bronze![e-mail]
Subject: Baymod-9/Baycom
To: [e-mail]

Hello,

I've recently acquired my first packet device, Baymod-9, the
1200-baud_modem_in_a_DB-9-shell device, and am running the Baycom
terminal package, all from Paccomm. My experience so far has been
good, (the packaging of the Baymod-9 is a little cheesy) and I like the
Baymod software. What we haven't been able to get running on this
modem is KA9Q NOS with the AX25.com packet driver written by Pawel
Jolocha. Seems there's a problem receiving TCP/IP packets on the
serial port. The machine is a Zenith MinisPort...we have considered
the possibility that the machine's port is too slow, but we tried a
faster Zenith too. Any ideas?

N9LKL,
John


--
**    Any opinions expressed are entirely my own, not my employers.     **
*     John Stigall - Indiana University Computing Services Network       *
**    [e-mail]  > Ham Radio: [e-mail] <    **

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

Date: 18 May 92 15:35:34 GMT
From: usc!zaphod.mps.ohio-state.edu!samsung!noose.ecn.purdue.edu!en.ecn.purdue.edu![e-mail]
Subject: CELLNET info needed
To: [e-mail]

    Help!  I am looking for more information on the 430 MHz 56 kbaud CELLNET
prototype station used between Napierville and Aurora IL.  I have already
downloaded the file from tomcat but need more information, particularly on the
PacketTEN 5port Stand-Alone NosInABox.

    So if wb9mjn, k9vxw, n4pcr, or anyone else with access to the project
could get back to me with a little more information, maybe I could this part
of Indiana out it's political and geographical black hole.

        Thanks,

            Tim             [e-mail]
                    [e-mail]

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

Date: 18 May 1992 06:52:25 -0700
From: [e-mail]
Subject: Digicom Wanted - third try
To: [e-mail]

Hello!
       I'm trying to put together a packet station from scratch after getting
interested in it through reading. My budget is tiny :-), so I've obtained a
secondhand Commodore 64 and am aiming at getting licensed in November when
the next Uk Radio Amateurs Exam happens. In the meantime I'm looking for the
Digicom software and construction details/schematic for its associated Bell 202
modem.

Can anyone send these to me or post info on where they can be obtained by ftp
or mail file-server? The C64 will soon have an RS232 interface and then C64/128
Kermit, so downloads should be possible.

I'm interested in TCP/IP but participation in AMPRNET will have to wait until
PC prices go lower.

Thanks in Advance!
          Steve Rudman

PS If I've assumed wrong and Digicom is *not* freely copyable for am rad
purposes then the address of a dealer stocking it in the UK would be useful.

 Janet:  "hooke::icarus::rudman" @ uk.ac.ox.atm.isams
-or-
 Janet:  umeeb37 @ uk.ac.ic.cc.vaxa   (if my local host is down)

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

Date: 17 May 92 15:24:55 GMT
From: ddi1!lrark![e-mail]
Subject: HamNet?
To: [e-mail]

In article <[e-mail]> [e-mail] (Karen Bourque) writes:
 >Hi.  I know nothing about Ham radios, I'm inquiring for a
 >person who doesn't have access to this net (yet).
 >
 >He's heard of something like a computer network for Ham
 >radio operators.  I've yet to find anything of the sort!
 >Anyone out there have any clue as to what he's talking about?
 >
 >Thanks
 >
 >Karen
 >
Well Karen, welcome to computers... HamNet has been in existence since the
early 80's using Compuserve "go hamnet" and is in existence on General
Electric (GEnie) "radio". Join in and have fun, we have for many years.

73

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

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

Date: 19 May 92 00:26:31 GMT
From: swrinde!mips!spool.mu.edu!agate!usenet.ins.cwru.edu!news.ysu.edu![e-mail]
Subject: NOS
To: [e-mail]

I am going to be getting my TNC soon and I was wondering what is
involved with connecting to InterNet and if I can telnet to other
sites and if FTP is possible.   Sorry if I sound ignorant.
--
Happiness is MANDATORY
James Stephens KD6DPM
Internet: [e-mail] or [e-mail]

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

Date: 18 May 92 16:26:26 GMT
From: mcsun!uknet!mucs![e-mail]
Subject: NOS for Unix
To: [e-mail]

You can also find the linux stuff (with local MCC mods) on
hpb.mcc.ac.uk

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

End of Packet-Radio Digest V92 #134
******************************
Date: Wed, 20 May 92 04:30:02 PDT
From: Packet-Radio Mailing List and Newsgroup <[e-mail]>
Errors-To: [e-mail]
Reply-To: [e-mail]
Precedence: Bulk
Subject: Packet-Radio Digest V92 #135
To: packet-radio


Packet-Radio Digest         Wed, 20 May 92       Volume 92 : Issue 135

Today's Topics:
     BAYCOM15.ZIP - Packet Radio term program for PCs without TNC
             don't forget America Online
            HS Modems List Address
         NOS for Unix? Fast radio modems? Gatewaying?

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 May 1992 18:00:43 -0700
From: [e-mail]
Subject: BAYCOM15.ZIP - Packet Radio term program for PCs without TNC
To: [e-mail]

I have uploaded to WSMR-SIMTEL20.Army.Mil:

pd1:<msdos.packet>
BAYCOM15.ZIP    Packet Radio term program for PCs without TNC

Baycom is a packet radio program including software and hardware to
receive and transmit packet radio by using a MS-DOS computer and a
2 meter transceiver.

'73 Freerk PE1OPI

e-mail : [e-mail]
The Netherlands.

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

Date: 19 May 1992 07:23:31 -0700
From: [e-mail]
Subject: don't forget America Online
To: [e-mail]

Karen.... as well as Compu$erve and GEnie, there is a Ham Radio Club on
America Online too! At last count we had over 500 hams, swlers, scanner
users as electronics enthusiasts registered. Lots of files in our libraries
too.

All you need is a PC (or any DOS machine), a Mac or and an Apple //e and the
software is FREE. Call 1-800-227-6364 Ext 5254 to get the software. I am not
too biased... but AOL is a LOT friendlier to use if you have ANY experience
with a GUI (graphics user interface)... I have a Mac.

If you would rather send me your address via private e-mail. I'll have the
software mailed right to you directly.

Terry - [e-mail], America Online-TSTADER-Ham Radio Club Host
KA8SCP@WA1PHY.#EMA.MA.USA.NA or [e-mail] [44.56.4.82]
A Macintosh TCP/IP Station

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

Date: 20 May 92 03:04:30 GMT
From: swrinde!cs.utexas.edu!usc!sol.ctr.columbia.edu!destroyer!ubc-cs!alberta!canada![e-mail]
Subject: HS Modems List Address
To: [e-mail]

Does anyone have a non-ampr.org address for the [e-mail]
mailing list? I can't seem to get to the ampr.org address from my end
of the Internet. Thanks.

--lyndon

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

Date: 18 May 92 23:35:02 GMT
From: dog.ee.lbl.gov!nosc!crash!nusdecs!arghouse![e-mail]
Subject: NOS for Unix? Fast radio modems? Gatewaying?
To: [e-mail]

[e-mail] (Dan Brown) writes:

> There are several problems that we know that we have to consider... like:
>
> "How do you keep people from just adding themselves to the net?"
> "How can you expect this to be anywhere near private?"
> "How can you keeps this secure?"
> etc...
>

1)      Adding yourself to a net is just like adding yourself to any other
meeting roster - someone must approve it.  If you call any network - packet,
CIS, Internet, etc. - you should have a proper password and user id.  If the
host doesn't recognize you, you don't exist in the net.

2)      Privacy can only be accomplished - over the air - by encoding your
data.  While this may slow things down, you could experiment with sub
carriers and encryption digitizing.  Seeing how the military can encrypt
data for secure radio nets, it seems that a civilian equivalent may exist.

3)      See 2).

If your WAN is line of sight, and you are going to use a commercial license
- which is needed to encrypt the data - then you might want to look at
microwave of UHF.  One site must act as server, and should have an antenna
dish pointed to each remote site.  The transmissions can be a tight beam
which has little side emmission, thus a low possibility of interception.
The higher the frequency of your carrier, the faster your modem can be.  If
you run high enough, you could use multiple sub carriers, switching one or
more on a regular or irregular basis.  If you use microwave, simple
encryption can be used, as the transmission would be a very tight beam and
quite difficult to intercept.

------------------
The Listening Post, San Diego, CA, USA  [phone]
Opinions expressed are those of [e-mail].

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

End of Packet-Radio Digest V92 #135
******************************
Date: Thu, 21 May 92 04:30:03 PDT
From: Packet-Radio Mailing List and Newsgroup <[e-mail]>
Errors-To: [e-mail]
Reply-To: [e-mail]
Precedence: Bulk
Subject: Packet-Radio Digest V92 #136
To: packet-radio


Packet-Radio Digest         Thu, 21 May 92       Volume 92 : Issue 136

Today's Topics:
          followup on Ramsey Electronics... (2 msgs)
           Looking for 70cm I&Q Demodulator
            [e-mail]
              Packet vs Internet
         Rejected posting to I-PACRAD@UIUCVMD

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: Wed, 20 May 1992 15:40:25 GMT
From: usc!zaphod.mps.ohio-state.edu!uwm.edu!ux1.cso.uiuc.edu!news.cso.uiuc.edu!uxa.cso.uiuc.edu![e-mail]
Subject: followup on Ramsey Electronics...
To: [e-mail]

Just a followup on my posting about Ramsey Electronics:

    1)  I have gotten no positive reports about Ramsey kits.  In fact,
there was only *one* response to my original posting, and it was also negative
and from a guy who had bought one of Ramsey's VHF transceiver kits.

    2)  In hindsight, the Ramsey kits are ridiculously overpriced for what
you get in the way of the quality of the circuit design and the documentation.
For example, the VHF transceiver kits run $180 to $190 for a *kit* which you
have to assemble, debug and which have only 10 diode-programmable frequencies,
compared to $230 or so for an Alinco "data radio" which is assembled and has
synthesized tuning.  (don't let anybody tell you that it "costs" more to put out
a kit... think about it.)

    3)  The Ramsey packet modem kit cost me $70 on a Dayton "special".
It is basically a Baycom circuit with little documentation other than assembly
instructions.  You can get Baycom "kits" for $40, and the Baycom documentation
goes much farther to explain to you how to get on the air.

    4)  And whatever you do, don't *assemble* your Ramsey kit.  They
won't give you a refund in that case.  :-)  (although I haven't given up yet!)


I wish that somebody had warned *me* about Ramsey before I plunked down my
$70.  sigh.


73 de kb8cne, Brad Banko

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

Date: Wed, 20 May 1992 17:47:30 GMT
From: theory.TC.Cornell.EDU![e-mail]
Subject: followup on Ramsey Electronics...
To: [e-mail]

In article <[e-mail]> [e-mail] (Bradley T Banko) writes:
[ ... stuff about expensive Ramsey kits ... ]

>synthesized tuning.  (don't let anybody tell you that it "costs" more to put out
>a kit... think about it.)

It often costs more to "make" kits than assembled products.  There was a long
thread about this a few months back on 'sci.electronics' about the demise of
Heathkit.  The two biggies that make kits expensive are volume and complexity.

Production of assembled components in high volumes is surprisingly cheap.  Kit
companies never seem to get the volume they need.  Supposedly, at the very end
Heath was still hand-stuffing components into little baggies.

Kits often can't be as complex as assembled products.  Look inside your HT
and think about hand assembling it.  Kit builders usually don't have the test
equipment that the production line and service tech have.  Finally, kits are
designed to be built and *work*, usually at the expense of performance.

It is getting to the point where food is the only thing you can save on by
making yourself.

--
=  =  =  =  =  =  =  =  =  =  =  =  =  =  =  =  =  =  =  =  =  =  =  =  =  =  =
Andrew C. Payne, N8KEI        UUCP:  ...!cornell!batcomputer!payne
              INTERNET:  [e-mail]

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

Date: 21 May 92 00:10:31 GMT
From: bionet!raven.alaska.edu!flux.isr.alaska.edu![e-mail]
Subject: Looking for 70cm I&Q Demodulator
To: [e-mail]

Ideally, I'd like to find a box that takes in a fixed 70cm-band frequency
and puts out baseband in-phase and quadrature signals.  But I'd settle for
an I&Q demodulator module that would work at or below these frequencies.
The only modules that I've seen so far are for higher frequencies up in
the cell phone range.  I'm just trying to get out of having to tweak
individual mixers.

Any leads to sources for such things would be appreciated.
Thanks,
--
Don Rice                   E-mail: [e-mail]    (Internet)
Geophysical Institute              fnddr@alaska               (BITNET)
University of Alaska               flux::ddr                  (SPAN)
Fairbanks, AK 99775        Phone:  [phone]        Loran: 64.86N 212.16E

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

Date: 20 May 1992 06:52:13 -0700
From: [e-mail]
Subject: [e-mail]
To: [e-mail]

Hi Packeters...

What is the ftp site for the tcpip programm NETMAC for Mac ?
Thanks.

George Alexiou
Dept. of Computer Eng.
Univ. Of Patras
Patras Greece

e-mail [e-mail]

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

Date: 20 May 92 17:27:06 GMT
From: swrinde!gatech!psuvax1!uxa.ecn.bgu.edu!garrot.DMI.USherb.CA![e-mail]
Subject: Packet vs Internet
To: [e-mail]

Is it possible to send mail to packet users via Internet (read news).
And by the way is it possible to do the same from packet to internet.

Also, can you tell me if there is a node in Canada or in Eastern USA.

    Thanks a lot !

    Martin Laforce
    Sherbrooke Canada
    VE2 MLU

    7-3

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

Date: 20 May 1992 06:56:46 -0700
From: [e-mail]
Subject: Rejected posting to I-PACRAD@UIUCVMD
To: [e-mail]

Your message is being returned to you unprocessed because it seems to have been
already sent to the I-PACRAD list. That  is, a message with identical body (but
possibly different headers) has been posted to the list recently, either by you
or by  someone else. If you  have a good reason  to resend this message  to the
list (for instance because half of the outbound spool files were lost in a disk
crash at  some intermediate node),  please alter the  message text in  some way
before resending  it. Note that  altering the  "Subject:" line or  adding blank
lines at the top or bottom of the message is not sufficient; you should instead
add a line  at the top explaining  why you are re-sending the  message, for the
benefit of the list membership.

------------------------ Rejected message (150 lines) -------------------------
Received: from CUNYVM.BITNET by VMD.CSO.UIUC.EDU (Mailer R2.07) with BSMTP id
 9723; Wed, 20 May 92 08:54:38 CDT
Received: from CUNYVM by CUNYVM.BITNET (Mailer R2.08) with BSMTP id 6190; Wed,
 20 May 92 09:53:16 EDT
Received: from ucsd.edu by CUNYVM.CUNY.EDU (IBM VM SMTP V2R2) with TCP;
   Wed, 20 May 92 09:53:14 EDT
Received: by ucsd.edu; id AA25693
    sendmail 5.64/UCSD-2.2-sun
    Wed, 20 May 92 04:30:05 -0700 for
 claris!voder!nsc!gpo.nsc.com!sinclair%spi.dnet
Received: by ucsd.edu; id AA25688
    sendmail 5.64/UCSD-2.2-sun
    Wed, 20 May 92 04:30:04 -0700 for /usr/lib/sendmail -oc -odb
 -oQ/var/spool/lqueue -oi -fpacket-radio-relay packet-radio-list
Message-Id: <[e-mail]>
Date: Wed, 20 May 92 04:30:02 PDT
From: Packet-Radio Mailing List and Newsgroup <[e-mail]>
Errors-To: [e-mail]
Reply-To: [e-mail]
Precedence: Bulk
Subject: Packet-Radio Digest V92 #135
To: [e-mail]


Packet-Radio Digest         Wed, 20 May 92       Volume 92 : Issue 135

Today's Topics:
     BAYCOM15.ZIP - Packet Radio term program for PCs without TNC
             don't forget America Online
            HS Modems List Address
         NOS for Unix? Fast radio modems? Gatewaying?

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 May 1992 18:00:43 -0700
From: [e-mail]
Subject: BAYCOM15.ZIP - Packet Radio term program for PCs without TNC
To: [e-mail]

I have uploaded to WSMR-SIMTEL20.Army.Mil:

pd1:<msdos.packet>
BAYCOM15.ZIP    Packet Radio term program for PCs without TNC

Baycom is a packet radio program including software and hardware to
receive and transmit packet radio by using a MS-DOS computer and a
2 meter transceiver.

'73 Freerk PE1OPI

e-mail : [e-mail]
The Netherlands.

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

Date: 19 May 1992 07:23:31 -0700
From: [e-mail]
Subject: don't forget America Online
To: [e-mail]

Karen.... as well as Compu$erve and GEnie, there is a Ham Radio Club on
America Online too! At last count we had over 500 hams, swlers, scanner
users as electronics enthusiasts registered. Lots of files in our libraries
too.

All you need is a PC (or any DOS machine), a Mac or and an Apple //e and the
software is FREE. Call 1-800-227-6364 Ext 5254 to get the software. I am not
too biased... but AOL is a LOT friendlier to use if you have ANY experience
with a GUI (graphics user interface)... I have a Mac.

If you would rather send me your address via private e-mail. I'll have the
software mailed right to you directly.

Terry - [e-mail], America Online-TSTADER-Ham Radio Club Host
KA8SCP@WA1PHY.#EMA.MA.USA.NA or [e-mail] [44.56.4.82]
A Macintosh TCP/IP Station

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

Date: 20 May 92 03:04:30 GMT
From:
 swrinde!cs.utexas.edu!usc!sol.ctr.columbia.edu!destroyer!ubc-cs!alberta!canada!
 [e-mail]
Subject: HS Modems List Address
To: [e-mail]

Does anyone have a non-ampr.org address for the [e-mail]
mailing list? I can't seem to get to the ampr.org address from my end
of the Internet. Thanks.

--lyndon

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

Date: 18 May 92 23:35:02 GMT
From: dog.ee.lbl.gov!nosc!crash!nusdecs!arghouse![e-mail]
Subject: NOS for Unix? Fast radio modems? Gatewaying?
To: [e-mail]

[e-mail] (Dan Brown) writes:

> There are several problems that we know that we have to consider... like:
>
> "How do you keep people from just adding themselves to the net?"
> "How can you expect this to be anywhere near private?"
> "How can you keeps this secure?"
> etc...
>

1)      Adding yourself to a net is just like adding yourself to any other
meeting roster - someone must approve it.  If you call any network - packet,
CIS, Internet, etc. - you should have a proper password and user id.  If the
host doesn't recognize you, you don't exist in the net.

2)      Privacy can only be accomplished - over the air - by encoding your
data.  While this may slow things down, you could experiment with sub
carriers and encryption digitizing.  Seeing how the military can encrypt
data for secure radio nets, it seems that a civilian equivalent may exist.

3)      See 2).

If your WAN is line of sight, and you are going to use a commercial license
- which is needed to encrypt the data - then you might want to look at
microwave of UHF.  One site must act as server, and should have an antenna
dish pointed to each remote site.  The transmissions can be a tight beam
which has little side emmission, thus a low possibility of interception.
The higher the frequency of your carrier, the faster your modem can be.  If
you run high enough, you could use multiple sub carriers, switching one or
more on a regular or irregular basis.  If you use microwave, simple
encryption can be used, as the transmission would be a very tight beam and
quite difficult to intercept.

------------------
The Listening Post, San Diego, CA, USA  [phone]
Opinions expressed are those of [e-mail].

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

End of Packet-Radio Digest V92 #135
******************************

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

End of Packet-Radio Digest V92 #136
******************************
Date: Fri, 22 May 92 04:30:03 PDT
From: Packet-Radio Mailing List and Newsgroup <[e-mail]>
Errors-To: [e-mail]
Reply-To: [e-mail]
Precedence: Bulk
Subject: Packet-Radio Digest V92 #137
To: packet-radio


Packet-Radio Digest         Fri, 22 May 92       Volume 92 : Issue 137

Today's Topics:
       Can 9600 baud and 1200 baud modems use the same channel?
             CELLNET info needed
          followup on Ramsey Electronics... (2 msgs)
          Help! PK232MBX and TAPR 9600 modem
      One $40 Baycom packet modem kit reference (repost)
               Relay and Baycom

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: Thu, 21 May 1992 20:27:34 GMT
From: news.acns.nwu.edu!casbah.acns.nwu.edu![e-mail]
Subject: Can 9600 baud and 1200 baud modems use the same channel?
To: [e-mail]

I am in the process of puting a TAPR 9600 baud modem kit together.  I
currently use a crystal controlled rig, Drake TR22 for packet on 2 m.
Can I use the same channel for 9600 baud packet?  (Of course, I would
only be able connect to others with similar capability. )

Rajiv
aa9ch
[e-mail]

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

Date: Thu, 21 May 92 22:05:11 GMT
From: usc!zaphod.mps.ohio-state.edu!magnus.acs.ohio-state.edu!usenet.ins.cwru.edu!slc8![e-mail]
Subject: CELLNET info needed
To: [e-mail]

In an earlier posting [e-mail] (Tim Miller) writes:
>
>
>       Help!  I am looking for more information on the 430 MHz 56 kbaud CELLNET
>prototype station used between Napierville and Aurora IL.  I have already
>downloaded the file from tomcat but need more information, particularly on the
>PacketTEN 5port Stand-Alone NosInABox.

Can you send me a copy of the file, or tell me where to get it??



--
Dan Brown
[e-mail]

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

Date: 21 May 92 15:03:56 GMT
From: csus.edu!netcomsv!mork![e-mail]
Subject: followup on Ramsey Electronics...
To: [e-mail]

In article <[e-mail]>, [e-mail] (Bradley T Banko) writes:
>
> Just a followup on my posting about Ramsey Electronics:
>
>       1)  I have gotten no positive reports about Ramsey kits.  In fact,
> there was only *one* response to my original posting, and it was also negative
> and from a guy who had bought one of Ramsey's VHF transceiver kits.

Ok.  Here is someone who thinks the Ramsey kits are a good deal. I
bought one in Dayton last year (the 2m transceiver) and had a great
time building it.  The diode programming was exactly what I was
looking for since I had in mind computer remote control of the
radio.   Were there some problems with the radio.  Yeah, but I had
pretty good support from Ramsey when I called, and I changed the
design in a couple simple ways that made the rig work near spec,
and be legal ;-)  I had a great time putting it together, and learned
a heck of lot more about RF engineering in this one project than
the last 18 years of licensed operations has tought me!

>       2)  In hindsight, the Ramsey kits are ridiculously overpriced for what
> you get in the way of the quality of the circuit design and the documentation.
> For example, the VHF transceiver kits run $180 to $190 for a *kit* which you
> have to assemble, debug and which have only 10 diode-programmable frequencies,
> compared to $230 or so for an Alinco "data radio" which is assembled and has
> synthesized tuning.  (don't let anybody tell you that it "costs" more to put out
> a kit... think about it.)

Well, then you're being ignorant if you don't listen to them.  Cuz
it isn't that cheap.  I've just recently gone through the exercise of
looking into what it would cost to market a kit, and still make some
profit off of it.  The design I did is considerably simpler than
the Ramsey radios, and mostly a digital design.  The cost of the
PCB was going to run between $10 and $15 in quantity.  The parts
cost was going to be about $30 in quantity.  A reasonable manual
costs $2, and packaging of the kit another $3.  So you have $40 for
the basic package.  There is a standard multiplier of 4 to account
for all of the distribution, R&D, and marketing costs.  That puts
the kit right at $120.  When I looked at what it would cost me up
front in detail I found the times 4 multiplier off, and the actual
cost was going to be about $160 for me to make a $10 per unit
profit.  After all is said and done, it turns out that something
of this complexity level just can't be sold for less than about
$150.    You claim that it can't cost more to put out a kit, well
actually, assembly and test time are significant, and would probably
add $20 to the $40 cost of my unit.  Considering how they are
marketing the unit, I'm impressed with what they've been able
to achieve!

>       3)  The Ramsey packet modem kit cost me $70 on a Dayton "special".
> It is basically a Baycom circuit with little documentation other than assembly
> instructions.  You can get Baycom "kits" for $40, and the Baycom documentation
> goes much farther to explain to you how to get on the air.

I can't speak to this, no experience with that kit.

>       4)  And whatever you do, don't *assemble* your Ramsey kit.  They
> won't give you a refund in that case.  :-)  (although I haven't given up yet!)

> I wish that somebody had warned *me* about Ramsey before I plunked down my
> $70.  sigh.
>
> 73 de kb8cne, Brad Banko

If you were trying to save $30 bucks, or the equivalent with the
transceiver, then you missed the whole point of the exercise of
buying a kit.

Steve KA6S

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

Date: 21 May 92 14:56:13 GMT
From: swrinde!mips!spool.mu.edu!hri.com!noc.near.net!uhasun!arrlhq![e-mail]
Subject: followup on Ramsey Electronics...
To: [e-mail]

In rec.radio.amateur.misc, [e-mail] (Andrew Payne) writes:

<kit thread history deleted.>

>Kits often can't be as complex as assembled products.  Look inside your HT
>and think about hand assembling it.  Kit builders usually don't have the test
>equipment that the production line and service tech have.  Finally, kits are
>designed to be built and *work*, usually at the expense of performance.

>It is getting to the point where food is the only thing you can save on by
>making yourself.

Last year I put together a garden. These were my costs:

1. 8 Tomato plants @ $0.69 each
2. 4 Basil plants @ $1.19 each
3. Bag o' lime: $2.39
4. Garden hose: $8.95
5. Shovels, rakes, other implements of destruction: approx $30.00
6. Trips to the garden store (round trip 12 miles at $0.25/mi): $3.00
7. Owl scarecrow to scare away the **^&^&^ squirrel: $9.95

Total: 64.57

Item #7 was entirely ineffective. The squirrel never managed to learn that
he didn't like green tomatoes. He would pick one, take one bite, then
toss it on the ground in disgust. The process was repeated often.

I finally got about 4 tomatoes. This averaged $16.14 per tomato. Next time
I will forgo the kit and buy the assembled product at the produce section
of the grocery store. Food can be expensive, but not nearly as bad as the
do-it-myself version. :-) (All in the spirit of good fun!)

73, Ed
-----
Ed Hare, KA1CV                  | [e-mail]
American Radio Relay League     | uhasun!arrlhq!ehare
225 Main St.                    |
Newington, CT  06111            | There is no limit to what you can
[phone] - voice          | accomplish if you don't care who
Senior ARRL Laboratory Engineer | gets the credit. - Harry S Truman
RFI, xmtr and rcvr testing      |
-----

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

Date: Thu, 21 May 1992 20:20:41 GMT
From: news.acns.nwu.edu!casbah.acns.nwu.edu![e-mail]
Subject: Help! PK232MBX and TAPR 9600 modem
To: [e-mail]

I purchased a TAPR 9600 baud modem kit along with the disconnect and
DCD kits.  Looking thru the modem manual they mention that they
haven't gotten around to figuring out the interface with the AEA PK 232 MBX.
They have a section on Pk 232 , an older one with a daughter board for mail.
But they do not have instructions for the PK232 MBX.  The instructions for
the PK 232 call for connections to the daughter board which my unit does not
have.

I would appreciate any information on interfacing the modem with my TNC.

Thanks
Rajiv
aa9ch
[e-mail]

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

Date: Thu, 21 May 1992 19:04:56 GMT
From: usc!zaphod.mps.ohio-state.edu!uwm.edu!ux1.cso.uiuc.edu!news.cso.uiuc.edu!uxa.cso.uiuc.edu![e-mail]
Subject: One $40 Baycom packet modem kit reference (repost)
To: [e-mail]

Here is a repost of *one* reference to a $40 Baycom packet modem kit that
I have seen.  Poor Man's Packet also has kits (/schematics) available for
on the order of $40.

73 de kb8cne, Brad Banko

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

Date: Sun, 17 May 92 21:30:55 -0500
From: Warren Kinninger <[e-mail]>
Subject: Relay and Baycom
To: [e-mail]

The RTTY column in the latest 73 mag has a description of a new relay
replacement using pin diodes. It's called the Ameriton QSK-5. It's actually
for linear amps and handles 2500 watts. It says it is installed using cables
without internal wiring (I don't understand this). It's made by Ameriton in
Starkville, MS 800/647-1800.

Also Craig Rader N4PLK has Baycom kits for $45 unassembled or $55 assembled.
plus $2.50 shipping and handling.
He's at 385 Cherokee Court, Altamonte Springs, FL 32701.

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

End of Packet-Radio Digest V92 #137
******************************
Date: Sat, 23 May 92 04:30:03 PDT
From: Packet-Radio Mailing List and Newsgroup <[e-mail]>
Errors-To: [e-mail]
Reply-To: [e-mail]
Precedence: Bulk
Subject: Packet-Radio Digest V92 #138
To: packet-radio


Packet-Radio Digest         Sat, 23 May 92       Volume 92 : Issue 138

Today's Topics:
                BBS standards
             CELLNET info needed
               The BBS R: lines

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: 23 May 1992 03:35:38 -0700
From: [e-mail]
Subject: BBS standards
To: [e-mail]

     Seems like we've been through this one before.

     Since TCP/IP uses standards on the way things are done, and programs
like KA9Q's NOS/Net are so flexible and follow a few basic rules, I can
far exceed the mailing capabilities of any packet BBS out there. One of
the biggest problems I'm having now is with the incompatibility of the
message formats.
     I have absolutely no problems when an AX25 BBS forwards to a NOS
system or mail comes in by  NNTP, SMTP, etc..., but since the BBS's can't
handle existing world-wide standards, do we have to keep modifying the
programs out there to follow non-standard practices that the AX25 BBS's
are using?
     Some versions of NOS (like PA0GRI and WG7J) have gone as far as
including a  SMTPTOO command which will remove the SMTP headers in a
message and replace it with an R: line. Why should you even have to
remove a standard like the format that the SMTP headers are in just
because the BBS sysops's complain about the long headers.  The headers
are there for AX25 forwarding too, but the software usually suppresses
them. Why not suppress SMTP headers too and leave them alone?
     Also the BBS programs can't seem to read the SMTP headers. They are
in a nice simple format and are very easy to read, so I don't see what's
so hard about adding it into their code.  When I send a message for both
distribution via SMTP and AX25 BBS and I send it from a NOS system, the
messages usually don't work correctly.  An example would be how I would
send a message to   all@detroit   on the TCP/IP side and also send it
to   TCPIP@SEMICH   on the BBS side. In header of the message there is a
 To: all@detroit   and a   Cc: TCPIP@SEMICH . When it gets forwarded to
an AX25 BBS, the message ends up as  all@detroi  (note 6 characters).
A NOS system can see headers coming in and know what to do with them. An
AX25 type packet BBS can only accept the   to@bbs < callsign  format
and always seems to get lost on the  hostname type formats. NOS can easily
be modified to handle whatever format the AX25 systems decide on, but it
should be a system that is upwardly compatible.
     So far I am seeing more and more new ideas popping up which is making
the AX25 type BBS's not upwardly compatible or catching up with programs
such as NOS.  I am dropping the BBS program that I use as a gateway (I've
run MSYS, AA4RE and F6FBB) and I'm going completely to a NOS system since
it can talk to about anything out there (TCP/IP, NETROM, AX25, can run
ethernet, do real networking, will support UPPER and lower case in a
script file, etc...) and there are far more capabilites in the program.
     Also please don't tell me that MSYS has TCP/IP, NETROM, etc...  I've
run it for years and the TCP/IP is badly broken and NETROM doesn't work
nearly as good as it should.  The TCP/IP is virtually useless in the
program.   If the BBS's can add in capabilities to handle other formats,
or at least the capability to handle an RFC standard, then they will
probably gain a little more popularity and be far more flexible.
     Before any responds about the work involved in a BBS, I have been a
BBS Sysop on several systems and am currently one on one of the largest
BBS's in the state of Michigan and I've run nearly every U.S. and
European BBS program that exists and I run the Detroit TCP/IP switch and
several NET/ROM nodes and just about every version of NOS/Net that there
is (IBM, Amiga, Mac  and nearly every version of each), so I am very
very familiar with the operation of the systems and what's involved.
     Looks like Phil wrote a fantastic program with his TCP/IP for packet
radio and I plan on replacing all the non-standard systems with NOS and
watch the BBS programs try to catch up.

Ron  N8FOW

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

Date: Sat, 23 May 1992 03:40:53 GMT
From: mjbtn!wilson![e-mail]
Subject: CELLNET info needed
To: [e-mail]

For those looking for info on the PacketTen 5 port NOS based
switch, you might Email Don Lemley (N4PCR) at [e-mail]
for info on the switch.  Our group is using one that covers the
Middle Tennessee area, and it has been up and running well since
around February of this year.  It is capable of megabit data rates
and from what I have seen, it seems to be a very reliable way to
implement TCP/IP / Netrom  and AX25 traffic.  It runs a ROM version
of NOS and is very flexible in configuration possibilities.
For those that do not like to take trips to the hill, it can
be configured remotely and supports Telnet capability.  Once it
is running with a minimum configuration the setup can be modified
remotely by packet or landline (with a modem).

Another thing that might be of interest, There is a list that
has been started for the gracilis equipment, it can be reached
by email by sending a SUBSCRIBE message to :  [e-mail]
Changes, bugs, and other things may be found on this list from time to time.
The Packeten Switch is a relatively new product, I do not work for them,
but have been very impressed with the effort this company has made to
improve the capability of amateur packet state of the art.

My .02 Worth...

Dave

--
David R. Wilson, WB4LHO
Smyrna, Tennessee USA
INET: [e-mail]
UUCP: ...!uunet!mjbtn!wilson!david

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

Date: 23 May 1992 02:57:21 -0700
From: [e-mail]
Subject: The BBS R: lines
To: [e-mail]

     Is there anything actually written down in some kind of formal type
format as to a standard for the R: lines in AX25 BBS's? I'm not looking
for just word of mouth or gentlemens agreement on how to do it since
that hasn't worked.
     Basically I've noticed some differences here.  Some systems will
have the city/info  section like  city [info] , some will be [info] city,
others have just a city, some  [city] info, etc...  Seems like
everyone does it different.  Normally I could care less about what is
after the hierarchical address since I just use it for general info, but
apparently the WP server does.  On an R: line like mine where it has
[IP TUNNEL] Roseville      the WP server will take what's in the brackets
and make that the city that I live in.  Some programs have an info
section and a QTH one for the R: line. The QTH is also used for things
like BEACONS and other BBS stuff while the info is put in brackets. Usually
if the program has an info option then it will put a  []  in the R:
line anyways.  If you flip the QTH and ifo then it will just put
out strange beacons over packet and you're more or less not even fixing
a problem but are just trying to go around it.
     I noticed that F6FBB program is putting the city in brackets and
the  FBB sig afterwards.  Works for the WP server though.
     How about making a standard to stick by and a few basic rules (like
R: lines being limited to 79 characters when you are at your max amount
of messages).  Some people say the info doesn't belong. Well I have
personally found them extremely helpful. It's usually only a few
characters anyways.

Ron  N8FOW

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

End of Packet-Radio Digest V92 #138
******************************
Date: Sun, 24 May 92 04:30:04 PDT
From: Packet-Radio Mailing List and Newsgroup <[e-mail]>
Errors-To: [e-mail]
Reply-To: [e-mail]
Precedence: Bulk
Subject: Packet-Radio Digest V92 #139
To: packet-radio


Packet-Radio Digest         Sun, 24 May 92       Volume 92 : Issue 139

Today's Topics:
            looking for .ampr.org gateway
               The BBS R: lines

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: 24 May 92 15:32:04 GMT
From: swrinde!cs.utexas.edu!wupost!waikato.ac.nz!aukuni.ac.nz!kcbbs![e-mail]
Subject: looking for .ampr.org gateway
To: [e-mail]

Hi,

Thanks for reading this.

Who knows of an Internet > AMSAT-DCE or HF  Gateway ?

regards,

Steve.

[e-mail]
[e-mail]
[e-mail]

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

Date: 23 May 1992 11:40:29 GMT
From: ucsd.edu![e-mail]
Subject: The BBS R: lines
To: [e-mail]

There are only a few casual documents describing the exchange protocol
and header contents for the ham BBS network.  There are conflicts
between those written by different authors - probably an outgrowth of
the independence of the authors of the software, and perhaps even a
leftover from the early days when some of the BBS writers were coding
FOR incompatability in an effort to force their way of doing things.

I am (as a background task, so don't hold your breath) attempting to
reconcile these various informal documents and come up with a standard
document that will describe a basic protocol that can be counted on to
work with nearly all existing BBS implementations, with the hope that
future BBS authors will be able to use it as a reference.

Right now, no such document exists.
    - Brian

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

End of Packet-Radio Digest V92 #139
******************************
Date: Mon, 25 May 92 04:30:03 PDT
From: Packet-Radio Mailing List and Newsgroup <[e-mail]>
Errors-To: [e-mail]
Reply-To: [e-mail]
Precedence: Bulk
Subject: Packet-Radio Digest V92 #140
To: packet-radio


Packet-Radio Digest         Mon, 25 May 92       Volume 92 : Issue 140

Today's Topics:
                BBS standards
            June 6th, 1991 6:24pm
              MFJ 1278 Problems
                newbie problem

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: 24 May 92 17:46:51 GMT
From: swrinde!gatech!usenet.ins.cwru.edu!ncoast![e-mail]
Subject: BBS standards
To: [e-mail]

As quoted from <[e-mail]> by [e-mail] (Ron Atkinson ):
+---------------
|      I have absolutely no problems when an AX25 BBS forwards to a NOS
| system or mail comes in by  NNTP, SMTP, etc..., but since the BBS's can't
| handle existing world-wide standards, do we have to keep modifying the
| programs out there to follow non-standard practices that the AX25 BBS's
| are using?
+---------------

Try to remember that SMTP "Received:" lines were designed for somewhat larger
systems than most PBBSes.  "R:" lines are somewhat shorter than "Received:"
lines... and with the number of them that can build up in a message, the space
savings can be considerable.

But if you're griping about that, you might as well complain about Fido
"SEEN-BY:", Usenet "Path:" and all the others as well.

+---------------
| because the BBS sysops's complain about the long headers.  The headers
| are there for AX25 forwarding too, but the software usually suppresses
| them. Why not suppress SMTP headers too and leave them alone?
+---------------

"R:" lines can be suppressed trivially:  they're a single physical line.
"Received:" lines are often multiline.

MSYS 1.13, however, does suppress "Received:" lines.

+---------------
|      Also the BBS programs can't seem to read the SMTP headers. They are
| in a nice simple format and are very easy to read, so I don't see what's
| so hard about adding it into their code.  When I send a message for both
+---------------

NOS SMTP headers are okay, but anyone who's tried to write an RFC822 parser
that will handle the headers of any mailer on the Internet can tell you just
how mich of a nightmare it really is.

+---------------
| and always seems to get lost on the  hostname type formats. NOS can easily
| be modified to handle whatever format the AX25 systems decide on, but it
| should be a system that is upwardly compatible.
+---------------

NOS is designed for interoperability with Internet, NOT for PBBSes.  The two
are vastly different environments in intent, and the implementation reflects
that.  I don't seriously believe that we'll be seeing SMTP become the AX.25
message format standard.

Consider this while you're at it:  more and more TNCs have personal mailboxes
with reverse forwarding, etc.  The chances of a TNC running SMTP for this are
zero:  it's too complex for the limited memory available in most TNCs.

++Brandon
--
Brandon S. Allbery, KF8NH [44.70.4.88]: [e-mail], [e-mail]
Senior Programmer, Telotech, Inc. (if I may call myself that...)

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

Date: 24 May 1992 23:51:52 -0700
From: [e-mail]
Subject: June 6th, 1991 6:24pm
To: [e-mail]

-----> Note that Jean-Bernard Condat and the Chaos Computer Club France
       work all the time for the diffusion of the packet-radio  in  the
       beautiful country of France!


DON'T HESITATE TO FOLLOW TO OTHER BULLETIN BOARDS THROUGHOUT THE WORLD.


               Juny 6th, 1991  6:24 pm

The French Police Judiciaire inculped of computer fraud (]462.2 of  the
French legislation) Jean-Bernard Condat, general secretary of the Chaos
Computer Club France (cccf).

The police said that like an hackers club (72 members in France)    and
1,800 correspondants throughout the world) cannot be legal and found  a
crazy story of NUI (the well known BND2 code used from two years by all
the people via Minitel, the French terminal) and inculped  Jean-Bernard
for paying US$1,000 pro month... "ad vita aeternam"!

The anniversary of this day, the CCCF make a great fest with a lot   of
articles on computer haching, etc. Don't hesitate to collaborate and/or
send a message in this e-mail box for Jean-Bernard.

Thank for your help. Don't hesitate to put this e-mail address on  your
mailing list... and to ask us for all your French questions.

(bureau of) Jean-Bernard Condat
Chaos Computer Club France (CCCF)
B.P. 8005
69351 Lyon Cedex 08, France
Tel.: [phone]
Fax.: [phone].

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

Date: 24 May 92 15:26:06 GMT
From: psgrain!qiclab!therose![e-mail]
Subject: MFJ 1278 Problems
To: [e-mail]

If anyone knows how to get the HF side working on a MFJ1278, I'd sure
like to hear about it. What should I be checking for? What is the Best
Program to use with it. I just picked up Lan-link 1.59 But Not sure this
is the best for this TNC. I got the VHF side working so far. TNX.

Rig here is a Kenwood 140s

73 De
                  Larry Lund
                   N7LBP/AG

Packet : N7LBP @ W7XI.OR.USA.PDX7


 * SLMR 2.1a #2073 * It's only a hobby ... only a hobby ... only a

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

Date: 24 May 1992 17:28:44 -0700
From: [e-mail]
Subject: newbie problem
To: [e-mail]

I just purchased an MFJ TNC-2, which I'm using on a Mac IIsi with an
FT-411e (employing "normal" off-the-shelf Mac-to-RS232 modem cable and
an pre-made MFJ cable from TNC-to-411). Now the computer is
communicating fine with the TNC, judging by the text display and
acceptance of commands. Also, the DCD light goes on when a packet comes
across the radio. But hitting the MONITOR command brings nothing to
the screen. Can anyone explain what I might be doing wrong without
actually seeing my setup? Thanks in advance...

  A  E
=-=-=-=-=-=-=-=
Andy Eddy-WB1FNV/6, 7J1ALH    Beverly Hills, California
Exec. Editor, VideoGames & Computer Entertainment Magazine
Internet: [e-mail] or [e-mail]
Delphi: VIDGAMES                  CompuServe: 70007,3554
GEnie: VIDGAME       MCImail: VIDGAMES          Prodigy: CKJB66A

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

End of Packet-Radio Digest V92 #140
******************************
Date: Tue, 26 May 92 04:30:03 PDT
From: Packet-Radio Mailing List and Newsgroup <[e-mail]>
Errors-To: [e-mail]
Reply-To: [e-mail]
Precedence: Bulk
Subject: Packet-Radio Digest V92 #141
To: packet-radio


Packet-Radio Digest         Tue, 26 May 92       Volume 92 : Issue 141

Today's Topics:
             ARRL Repeater Guide
                newbie problem
         Rejected posting to I-PACRAD@UIUCVMD

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: 25 May 1992 07:56:52 -0700
From: [e-mail]
Subject: ARRL Repeater Guide
To: [e-mail]

For anyone who has not noticed, the The ARRL Repeater Directory,
1992-1993 Edition apparently left Maryland and DC out of the
Packet section.  If you buy the $6 Guide, you better keep your old one
for an at least out dated listed of these.
--
David L. Wilson                 [e-mail]
Department of Mathematics       Amateur: AC4IU (ex-KD4ASW/KO4EQ)
Mary Washington College         Home Phone:    [phone]
Fredericksburg, VA  22401       Office Phone:  [phone]

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

Date: 25 May 92 13:48:15 GMT
From: cis.ohio-state.edu!pacific.mps.ohio-state.edu!linac!att!cbfsb!cbnewsb.cb.att.com![e-mail]
Subject: newbie problem
To: [e-mail]

In article <[e-mail]> [e-mail] (ANDY EDDY, VG&CE EXECUTIVE EDITOR) writes:
>I just purchased an MFJ TNC-2, which I'm using on a Mac IIsi with an
>FT-411e (employing "normal" off-the-shelf Mac-to-RS232 modem cable and
>an pre-made MFJ cable from TNC-to-411). Now the computer is
>communicating fine with the TNC, judging by the text display and
>acceptance of commands. Also, the DCD light goes on when a packet comes
>across the radio. But hitting the MONITOR command brings nothing to
>the screen. Can anyone explain what I might be doing wrong without

Maybe you have the TNC set up expecting 300 baud (for HF reception), when
you want 1200 Baud (for VHF)?  Or visa versa?  (not familiar with the 411,
is it HF or VHF or UHF rig?)  Or maybe you need to increase or decrease the
audio volume from your reciever (weak or distorted audio doesn't help decoding
any!).  A first guess is to set the volume where you'd use it for voice work.
Hope this helps.   73s

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

Date: 25 May 1992 07:45:32 -0700
From: [e-mail]
Subject: Rejected posting to I-PACRAD@UIUCVMD
To: [e-mail]

Your message is being returned to you unprocessed because it seems to have been
already sent to the I-PACRAD list. That  is, a message with identical body (but
possibly different headers) has been posted to the list recently, either by you
or by  someone else. If you  have a good reason  to resend this message  to the
list (for instance because half of the outbound spool files were lost in a disk
crash at  some intermediate node),  please alter the  message text in  some way
before resending  it. Note that  altering the  "Subject:" line or  adding blank
lines at the top or bottom of the message is not sufficient; you should instead
add a line  at the top explaining  why you are re-sending the  message, for the
benefit of the list membership.

------------------------ Rejected message (200 lines) -------------------------
Received: from CUNYVM.BITNET by VMD.CSO.UIUC.EDU (Mailer R2.07) with BSMTP id
 5003; Mon, 25 May 92 09:44:44 CDT
Received: from CUNYVM by CUNYVM.BITNET (Mailer R2.08) with BSMTP id 8810; Mon,
 25 May 92 10:43:17 EDT
Received: from ucsd.edu by CUNYVM.CUNY.EDU (IBM VM SMTP V2R2) with TCP;
   Mon, 25 May 92 10:43:16 EDT
Received: by ucsd.edu; id AA17369
    sendmail 5.64/UCSD-2.2-sun
    Mon, 25 May 92 04:30:06 -0700 for
 claris!voder!nsc!gpo.nsc.com!sinclair%spi.dnet
Received: by ucsd.edu; id AA17359
    sendmail 5.64/UCSD-2.2-sun
    Mon, 25 May 92 04:30:04 -0700 for /usr/lib/sendmail -oc -odb
 -oQ/var/spool/lqueue -oi -fpacket-radio-relay packet-radio-list
Message-Id: <[e-mail]>
Date: Mon, 25 May 92 04:30:03 PDT
From: Packet-Radio Mailing List and Newsgroup <[e-mail]>
Errors-To: [e-mail]
Reply-To: [e-mail]
Precedence: Bulk
Subject: Packet-Radio Digest V92 #140
To: [e-mail]


Packet-Radio Digest         Mon, 25 May 92       Volume 92 : Issue 140

Today's Topics:
                BBS standards
            June 6th, 1991 6:24pm
              MFJ 1278 Problems
                newbie problem

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: 24 May 92 17:46:51 GMT
From: swrinde!gatech!usenet.ins.cwru.edu!ncoast![e-mail]
Subject: BBS standards
To: [e-mail]

As quoted from <[e-mail]> by
 [e-mail] (Ron Atkinson ):
+---------------
|      I have absolutely no problems when an AX25 BBS forwards to a NOS
| system or mail comes in by  NNTP, SMTP, etc..., but since the BBS's can't
| handle existing world-wide standards, do we have to keep modifying the
| programs out there to follow non-standard practices that the AX25 BBS's
| are using?
+---------------

Try to remember that SMTP "Received:" lines were designed for somewhat larger
systems than most PBBSes.  "R:" lines are somewhat shorter than "Received:"
lines... and with the number of them that can build up in a message, the space
savings can be considerable.

But if you're griping about that, you might as well complain about Fido
"SEEN-BY:", Usenet "Path:" and all the others as well.

+---------------
| because the BBS sysops's complain about the long headers.  The headers
| are there for AX25 forwarding too, but the software usually suppresses
| them. Why not suppress SMTP headers too and leave them alone?
+---------------

"R:" lines can be suppressed trivially:  they're a single physical line.
"Received:" lines are often multiline.

MSYS 1.13, however, does suppress "Received:" lines.

+---------------
|      Also the BBS programs can't seem to read the SMTP headers. They are
| in a nice simple format and are very easy to read, so I don't see what's
| so hard about adding it into their code.  When I send a message for both
+---------------

NOS SMTP headers are okay, but anyone who's tried to write an RFC822 parser
that will handle the headers of any mailer on the Internet can tell you just
how mich of a nightmare it really is.

+---------------
| and always seems to get lost on the  hostname type formats. NOS can easily
| be modified to handle whatever format the AX25 systems decide on, but it
| should be a system that is upwardly compatible.
+---------------

NOS is designed for interoperability with Internet, NOT for PBBSes.  The two
are vastly different environments in intent, and the implementation reflects
that.  I don't seriously believe that we'll be seeing SMTP become the AX.25
message format standard.

Consider this while you're at it:  more and more TNCs have personal mailboxes
with reverse forwarding, etc.  The chances of a TNC running SMTP for this are
zero:  it's too complex for the limited memory available in most TNCs.

++Brandon
--
Brandon S. Allbery, KF8NH [44.70.4.88]: [e-mail], [e-mail]
Senior Programmer, Telotech, Inc. (if I may call myself that...)

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

Date: 24 May 1992 23:51:52 -0700
From: [e-mail]
Subject: June 6th, 1991 6:24pm
To: [e-mail]

-----> Note that Jean-Bernard Condat and the Chaos Computer Club France
       work all the time for the diffusion of the packet-radio  in  the
       beautiful country of France!


DON'T HESITATE TO FOLLOW TO OTHER BULLETIN BOARDS THROUGHOUT THE WORLD.


               Juny 6th, 1991  6:24 pm

The French Police Judiciaire inculped of computer fraud (]462.2 of  the
French legislation) Jean-Bernard Condat, general secretary of the Chaos
Computer Club France (cccf).

The police said that like an hackers club (72 members in France)    and
1,800 correspondants throughout the world) cannot be legal and found  a
crazy story of NUI (the well known BND2 code used from two years by all
the people via Minitel, the French terminal) and inculped  Jean-Bernard
for paying US$1,000 pro month... "ad vita aeternam"!

The anniversary of this day, the CCCF make a great fest with a lot   of
articles on computer haching, etc. Don't hesitate to collaborate and/or
send a message in this e-mail box for Jean-Bernard.

Thank for your help. Don't hesitate to put this e-mail address on  your
mailing list... and to ask us for all your French questions.

(bureau of) Jean-Bernard Condat
Chaos Computer Club France (CCCF)
B.P. 8005
69351 Lyon Cedex 08, France
Tel.: [phone]
Fax.: [phone].

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

Date: 24 May 92 15:26:06 GMT
From: psgrain!qiclab!therose![e-mail]
Subject: MFJ 1278 Problems
To: [e-mail]

If anyone knows how to get the HF side working on a MFJ1278, I'd sure
like to hear about it. What should I be checking for? What is the Best
Program to use with it. I just picked up Lan-link 1.59 But Not sure this
is the best for this TNC. I got the VHF side working so far. TNX.

Rig here is a Kenwood 140s

73 De
                  Larry Lund
                   N7LBP/AG

Packet : N7LBP @ W7XI.OR.USA.PDX7


 * SLMR 2.1a #2073 * It's only a hobby ... only a hobby ... only a

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

Date: 24 May 1992 17:28:44 -0700
From: [e-mail]
Subject: newbie problem
To: [e-mail]

I just purchased an MFJ TNC-2, which I'm using on a Mac IIsi with an
FT-411e (employing "normal" off-the-shelf Mac-to-RS232 modem cable and
an pre-made MFJ cable from TNC-to-411). Now the computer is
communicating fine with the TNC, judging by the text display and
acceptance of commands. Also, the DCD light goes on when a packet comes
across the radio. But hitting the MONITOR command brings nothing to
the screen. Can anyone explain what I might be doing wrong without
actually seeing my setup? Thanks in advance...

  A  E
=-=-=-=-=-=-=-=
Andy Eddy-WB1FNV/6, 7J1ALH    Beverly Hills, California
Exec. Editor, VideoGames & Computer Entertainment Magazine
Internet: [e-mail] or [e-mail]
Delphi: VIDGAMES                  CompuServe: 70007,3554
GEnie: VIDGAME       MCImail: VIDGAMES          Prodigy: CKJB66A

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

End of Packet-Radio Digest V92 #140
******************************

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

End of Packet-Radio Digest V92 #141
******************************
Date: Wed, 27 May 92 04:30:04 PDT
From: Packet-Radio Mailing List and Newsgroup <[e-mail]>
Errors-To: [e-mail]
Reply-To: [e-mail]
Precedence: Bulk
Subject: Packet-Radio Digest V92 #142
To: packet-radio


Packet-Radio Digest         Wed, 27 May 92       Volume 92 : Issue 142

Today's Topics:
          Help with land-line forwarding...
        hi speed modem project - help please!
              NOS plus F6FBB under G8BPQ
           Packet radio via FAX boards????
              Where to buy TCM3105 i.c.?

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 May 92 16:34:44 GMT
From: munnari.oz.au!spool.mu.edu!news.nd.edu!mentor.cc.purdue.edu!noose.ecn.purdue.edu!en.ecn.purdue.edu![e-mail]
Subject: Help with land-line forwarding...
To: [e-mail]

    I realize that this is a touchy subject for some, but is there
anyone out there who has land-line forwarding working under g8bpq & w0rli?
Or with NOS for that matter.

    We have a strange set of geographical and political problems here,
and the phone line is already here and working, and may provide an
expedient if not totally ham radio solution.

        Thanks in advance,

            Tim     [e-mail]
                [e-mail]

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

Date: Tue, 26 May 1992 23:48:16 GMT
From: munnari.oz.au!bunyip.cc.uq.oz.au!marlin.jcu.edu.au!solwarra.gbrmpa.gov.au![e-mail]
Subject: hi speed modem project - help please!
To: [e-mail]

Hi,

I have a project i would like to get started, but need some hardware
to make it work.  I am trying to set up a packet slip line from my
QTH to work using a 56kbps packet slip line.  I would like to run
BSD at home on a 486 box talking to a MIPS box at work, that has an
AT bus.

What i need to know is what hardware would be required to get the m/c's
talking at, say 56kbps or higher, over the radio.  I am aware that we
would be required to write the drivers to use say a PI board on the 486
BSD box & the MIPS.

I would appreciate if you could let me know what hardware, in regards
to modems and interface cards, is available to allow us to get this
project off the ground.

any help appreciated.
tnx cul 73's de wayne

--
Wayne Amisano (VK4KT)     _-_|\\    E-Mail - [e-mail]
Great Barrier Reef       /     \\   Phone  - [phone] (GMT+1000)
Marine Park Authority.   \_.-._/    Fax    - [phone]
Our's to use Wisely!          v     Mail   - GPO Box 1379, Townsville QLD 4810

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

Date: 27 May 92 01:15:28 GMT
From: mcdhup!viper![e-mail]
Subject: NOS plus F6FBB under G8BPQ
To: [e-mail]

A local BBS sysop here is looking to replace MSYS with NOS + F6FBB
under G8BPQ. So far he has succeeded in getting F6FBB and BPQ integrated
and is trying to integrate NOS with BPQ on a second PC to get it all
checked out. What we want to know is, can the F6FBB BBS and NOS run in
two separate Desqview windows and communicate with one another via g8bpq
with "virtual" comm ports, ie, inside the PC without physically tying
up 2 serial ports for communications between the two programs?

Thanks in advance.

Please direct replies to viper!kc2ky

73 for now.

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

Date: 26 May 92 20:43:50 GMT
From: sdd.hp.com!zaphod.mps.ohio-state.edu!caen!destroyer!ubc-cs!news.UVic.CA!ve7frg![e-mail]
Subject: Packet radio via FAX boards????
To: [e-mail]

We would like to get any information from anyone out there that is
experimenting with 9600bps packet via fax boards.  Things of interest
would be:

What radios have been used?
Were any mods done to the radios?
What fax boards were used?
What software was used?

We would really like to be able to run 9600 with KA9Q's NOS as tcp/ip is
the choice of protocols.  Any and all info appreciated.

Please feel free to respond to the group or by e-mail.  I will post
summary to the group.

----

George Farris - VE7FRG  Internet  : [e-mail]
            Amprnet   : [e-mail]
Sidney, B.C.            UUCP      : uunet!sol.uvic.ca!ve7frg!george
[phone]          Packet    : VE7FRG@VE7VBB.#ISLAND.BC.CAN.NOAM

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

Date: 26 May 1992 08:06:09 -0700
From: [e-mail]
Subject: Where to buy TCM3105 i.c.?
To: [e-mail]

Can anyone in this list please tell me where to mail order TCM3105 FSK modem i.
c. It is the one used in many TNC's and in BAYCOM modem.

BYCOM modem part list includes authors ID's DL8MBT and DG3RBU, and e-mail
addresses [e-mail] and [e-mail]. I tried both from
Bitnet and my message was not delivered.

Thanks.
       Harold Sanchez  <[e-mail]>

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

End of Packet-Radio Digest V92 #142
******************************
Date: Thu, 28 May 92 04:30:02 PDT
From: Packet-Radio Mailing List and Newsgroup <[e-mail]>
Errors-To: [e-mail]
Reply-To: [e-mail]
Precedence: Bulk
Subject: Packet-Radio Digest V92 #143
To: packet-radio


Packet-Radio Digest         Thu, 28 May 92       Volume 92 : Issue 143

Today's Topics:
             Digicom Availability
             help with kw tm401b
      REQSAT Satellite Mail Re-Router Program available
      RTTYGate RTTY><Packet Mail Gateway BBS Software Available

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 May 1992 08:05:36 -0700
From: [e-mail]
Subject: Digicom Availability
To: [e-mail]

Hello!
       I'm trying to put together a packet station from scratch after getting
interested in it through reading. My budget is tiny :-), so I've obtained a
secondhand Commodore 64 and am aiming at getting licensed in November when
the next Uk Radio Amateurs Exam happens. In the meantime I'm looking for the
Digicom software and construction details/schematic for its associated Bell 202
modem.

Can anyone send these to me or post info on where they can be obtained by ftp
or mail file-server? The C64 will soon have an RS232 interface and then C64/128
Kermit, so downloads should be possible.

I'm interested in TCP/IP but participation in AMPRNET will have to wait until
PC prices go lower.

Thanks in Advance!
          Steve Rudman

PS If I've assumed wrong and Digicom is *not* freely copyable for am rad
purposes then the address of a dealer stocking it in the UK would be useful.

 Janet:  "hooke::icarus::rudman" @ uk.ac.ox.atm.isams
-or-
 Janet:  umeeb37 @ uk.ac.ic.cc.vaxa   (if my local host is down)

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

Date: 27 May 1992 06:31:09 -0700
From: [e-mail]
Subject: help with kw tm401b
To: [e-mail]

Does anyone have a mod for a
kenwood tm401b that would allow
it to go down to 433.8. normal range
is 440 - 450. I have one I would like
to buy but need to go down to 433.8
for packet network.
--------------------------------------------------------
David M. Ihle   Internet        [e-mail]  |
WB5MSB  Amateur radio  WB5MSB@K4RY.#CENAL.AL.USA.NOAM  |
NOAA/National Weather Service   [phone] (voice) |
SE Ag Weather Service Center    [phone] (FTS)   |
Auburn University, Alabama      [phone] (FAX)   |
--------------------------------------------------------

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

Date: 28 May 92 05:37:30 GMT
From: munnari.oz.au!yoyo.aarnet.edu.au!sirius.ucs.adelaide.edu.au!arch.adelaide.edu.au![e-mail]
Subject: REQSAT Satellite Mail Re-Router Program available
To: [e-mail]

Following the growth of the number of BBS's in the Microsat satellite
Mail forwarding group there was a problem that arose in how users
got their mail sent to their nearest satellite gateway if they wanted
the message to go via satellite instead of via HF packet or Amtor.

As a result of this I wrote my version of the REQSAT server. There is
another version of REQSAT about written for the F6FBB BBS specifically
however my version should work with any BBS software that runs
a standard MBL type import/Export server function (eg W0RLI, AA4RE, WA7MBL,
F6FBB and others).

To use the server all users have to do is send a message to REQSAT @ the
station running the server and in the body of the message include a
second address line that is the final destination address. The server then
unwraps the message from the REQSAT header and re-addresses it to its
final destination.

While this software was designed primarily for use by the satellite gateways
it could be used by other systems that run wormholes so users can get
their mail sent to the nearest wormhole.

Till now I have only distributed the code via the satellites (which I dont
have direct access too) hence today I have uploaded it to two
AARNet/Internet sites.

For overseas users the REQSAT server program is available from:

tomcat.gsfc.nasa.gov  in /public/bbs/reqsat24.zip

For Australian Users it is available from:

grivel.une.edu.au  in /pub/ham-radio/incoming/reqsat24.zip

I hope to make a copy available on the UO-22 and AO-16 Microsats very
shortly. Comments on improvements people would like to see in the code are
most welcome.

Cheers de Grant VK5ZWI
--
Grant Willis (VK5ZWI) 3rd/4th Yr Elec. Eng. Stud.     | The opinions expressed
Adelaide University, South AUSTRALIA                  | here are mine. The
AARNet/Internet: [e-mail]  | Uni probably doesnt
Packet Radio: VK5ZWI@VK5TTY.#ADL.#SA.AUS.OC           | know I exist!

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

Date: 28 May 92 05:22:07 GMT
From: munnari.oz.au!yoyo.aarnet.edu.au!sirius.ucs.adelaide.edu.au!arch.adelaide.edu.au![e-mail]
Subject: RTTYGate RTTY><Packet Mail Gateway BBS Software Available
To: [e-mail]

For the past couple of years myself and Andrew VK5EX (who isn't on
AARNet/Internet) have been writing a RTTY BBS program with facilities
to be linked to the Packet BBS Mail network when run under a multitasking
program like DESQview on an IBM PC (or clone). We have released a couple of
earlier versions for general consumption but only distributed these by people
sending disks (we copied the code and mailed it back, a very slow
and time consuming process as you can imagine). Hence today I finally
have uploaded a copy of the program to two AARNet/Internet sites.

For overseas (ie not in Australia) users it is available on
tomcat.gsfc.nasa.gov via anonymous FTP as:

  /public/bbs/rttygate/rbb826a.exe

(small note here, the file rbb826.exe on tomcat is corrupt, I forgot to
set Binary mode before I started sending it!)

In Australia I have put it on grivel.une.edu.au as:

  /pub/ham-radio/incoming/rbb826.exe

This is a self-extracting file for IBM-PC machines and compatibles.

Some of the features of RTTYGate are:

* No need for an expensive data controller. RTTY (Baudot) code is produced
  direct on the serial port. All thats needed is an Audio Modem.

* Various list command options

* Supports Packet Mail H-addressing for exported mail

* Users can ask the BBS to change speed

* The system is capable of running most popular speeds between 45 and 300
  Baud.

There is a lot more in the program and a lot more planned. If you use RTTYGate
and would like to see a particular feature included send me a message
and I will add it to the wish list. RTTYGate is distributed FREE to
all amateur radio operators. Comercial use is however strictly forbidden.

Cheers de Grant VK5ZWI Co-Author RTTYGate BBS v8.26
--
Grant Willis (VK5ZWI) 3rd/4th Yr Elec. Eng. Stud.     | The opinions expressed
Adelaide University, South AUSTRALIA                  | here are mine. The
AARNet/Internet: [e-mail]  | Uni probably doesnt
Packet Radio: VK5ZWI@VK5TTY.#ADL.#SA.AUS.OC           | know I exist!

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

End of Packet-Radio Digest V92 #143
******************************
Date: Fri, 29 May 92 04:30:03 PDT
From: Packet-Radio Mailing List and Newsgroup <[e-mail]>
Errors-To: [e-mail]
Reply-To: [e-mail]
Precedence: Bulk
Subject: Packet-Radio Digest V92 #144
To: packet-radio


Packet-Radio Digest         Fri, 29 May 92       Volume 92 : Issue 144

Today's Topics:
                   ********
        Looking for Internet-Prodigy gateway !
                newbie problem

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 May 92 14:28:27 GMT
From: pa.dec.com!decuac!bobseg.enet.dec.com![e-mail]
Subject: ********
To: [e-mail]

Greetings,

Has anyone built or had any direct experience using the PMP modem and software?

Bob Segrest

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

Date: Thu, 28 May 92 07:32:07 PDT
From: RICHARD HAREL <[e-mail]>
Subject: Looking for Internet-Prodigy gateway !
To: [e-mail]

Is there a way I can send mail trough the internet to Prodigy ?
-Rich
WB2JBS
[e-mail]

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

Date: Tue, 26 May 1992 08:19:05 +1000
From: munnari.oz.au!jabaru.cec.edu.au!csource![e-mail]
Subject: newbie problem
To: [e-mail]

 > From: [e-mail] (ANDY EDDY, VG&CE EXECUTIVE EDITOR)
 > Organization: UCSD Usenet Gateway

 > I just purchased an MFJ TNC-2, which I'm using on a Mac IIsi with
 > an
 > FT-411e (employing "normal" off-the-shelf Mac-to-RS232 modem cable
 > and
 > an pre-made MFJ cable from TNC-to-411). Now the computer is
 > communicating fine with the TNC, judging by the text display and
 > acceptance of commands. Also, the DCD light goes on when a packet
 > comes
 > across the radio. But hitting the MONITOR command brings nothing
 > to
 > the screen. Can anyone explain what I might be doing wrong without
 > actually seeing my setup? Thanks in advance...

 >   A  E
 > =-=-=-=-=-=-=-=
 > Andy Eddy-WB1FNV/6, 7J1ALH    Beverly Hills, California
 > Exec. Editor, VideoGames & Computer Entertainment Magazine
 > Internet: [e-mail] or [e-mail]
 > Delphi: VIDGAMES                  CompuServe: 70007,3554
 > GEnie: VIDGAME       MCImail: VIDGAMES          Prodigy: CKJB66A

Andy,
  Its a long time since I've run my MFJ TNC's in other than KISS mode
but I seem to remember that there was a command like MNONAX25 ON/OFF
that had some bearing on the MONITOR command.  I just blew the dust
off my 1270B Manuals but I couldn't find the command mentioned in
there, but if you use the DISPLAY command or something like that it
will show you the command and its state, try swapping it ON/OFF, I
think, again from memory, that you had to turn it ON, to monitor
packets.

Bryan L. Weeks  VK3BLW
[e-mail]


 * Origin: The Raven_Haven BBS * * Trailblazer * PEP * * 61-3-593.1598 (3:632/403)

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

End of Packet-Radio Digest V92 #144
******************************
Date: Sat, 30 May 92 04:30:04 PDT
From: Packet-Radio Mailing List and Newsgroup <[e-mail]>
Errors-To: [e-mail]
Reply-To: [e-mail]
Precedence: Bulk
Subject: Packet-Radio Digest V92 #145
To: packet-radio


Packet-Radio Digest         Sat, 30 May 92       Volume 92 : Issue 145

Today's Topics:
               Packet BBS distributions
                 uo22
           UO22 uplink freqs? (help please)

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: 29 May 1992 20:46:59 GMT
From: ucsd.edu![e-mail]
Subject: Packet BBS distributions
To: [e-mail]

When ham packet BBS messages are sent, they are usually addressed to a
general subject area and a general distribution.  E.g., the send line is
something like

    SB  KEPS @ AMSAT

where the subject area (a primitive equivalent to a Usenet newsgroup) is
"KEPS", and the distribution is "AMSAT".

Presumably BBSs will have forwarding lists that can be set to forward
messages addressed to the distribution "AMSAT" to only those BBSs that
want to see it.  Of course, it is likely that the majority of these
BBSs will forward all but a few such distributions to their neighbors;
for example, I forward everything except a SDIEGO distribution to my
neighbor BBS in Los Angeles.

However, some time in the past, it seems that an agreement was reached
among a lot of the Southern California BBS Sysops that there were too
many of these distribution designators, thus causing confusion and a
maintenance problem for sysops.  These sysops decided they would only
forward a very few such distributions: ALLUS, ALLCA, ALLCAS, and a
city and/or countywide one.  All articles ("bulletins") entering one of
those BBSs would have its distribution address field REWRITTEN to one of
the acceptable few.

This strikes me as a particularly short-sighted decision.  However, not
being familiar with early BBS software, it may have been a convenient
method to simplify the maintenance of routing when dealing with stupid
software.

The AA4RE BBS package (with which I am most familiar, of the various
offerings) allows one to specify that distributions like "AMSAT" can
be TREATED as e.g., "ALLUS", without rewriting the field in the address.
Then the message can be distributed with much finer detail than can
currently done: for example, a DXers' BBS can ask its neighbors not to
feed it stuff from AMSAT.

This, to me, makes much more sense than rewriting the actual address.

Thus I think it's time for the people in my area to rethink their
current addressing scheme, particularly the rewriting addresses part.

Comments?
    - Brian

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

Date: Fri, 29 May 92 21:20:16 WIB
From: "Robby Soebiakto" <[e-mail]>
Subject: uo22
To: owpurbo@sunee

Onno, this may look strange, but i need the uplink freqs of UO-22. Could you
get the info from your sources? I discarded my @ AMSAT bulletins, and now i
need it! Thanks for helping me. Rob

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

Date: Fri, 29 May 1992 14:36:14 GMT
From: sdd.hp.com!cs.utexas.edu!utgpu!torn.onet.on.ca!watserv1!norton.waterloo.edu![e-mail]
Subject: UO22 uplink freqs? (help please)
To: [e-mail]

I just received an inquiry from my friend Robby YB1BG in Jakarta
on the uplink freqs of UO22. We would greatly appreciate any info.
Attach is his original mail. Thanks.
73 Onno YC1DAV/VE3
    [e-mail]

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

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

End of Packet-Radio Digest V92 #145
******************************
Date: Sun, 31 May 92 04:30:02 PDT
From: Packet-Radio Mailing List and Newsgroup <[e-mail]>
Errors-To: [e-mail]
Reply-To: [e-mail]
Precedence: Bulk
Subject: Packet-Radio Digest V92 #146
To: packet-radio


Packet-Radio Digest         Sun, 31 May 92       Volume 92 : Issue 146

Today's Topics:
                (none)
                BAYCOM & TCPIP
               Packet BBS distributions
         Rejected posting to I-PACRAD@UIUCVMD

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: 31 May 1992 00:59:25 -0700
From: [e-mail]
Subject: (none)
To: [e-mail]

Hi net-ers.
Do you know any source for the TMC3105 modem (I mean that they have it in stock"
George P Alexiou
[e-mail]

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

Date: 30 May 1992 14:50:36 -0700
From: [e-mail]
Subject: BAYCOM & TCPIP
To: [e-mail]

As PAWEL did not have packet access (he is not a ham yet ) a lot of
hams asked me to forward AX25DRV via packet network.
I send it but as many mail come back , most of bbs did not get it as I post
it using 7plus in 10Kb mails. So I ask from the hams that can forward it
to local BBS to do this so every one can get it.
Especialy in England if some one can forawrd it to G6WHL@GB7KLY or CLIVE@GB7KLY
as G4OYZ asked me to do this.
If it is possible send the version with SRC code so everyone can work
TCP/IP with a BAYCOM modem.
73 de
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
%           George Katsimaglis  SV1BDS [ KM17VX ] %
% QRV     : 145200 Khz , RU1 , 7088 Khz           %
% P-mail  : [e-mail]               %
% amprnet : [e-mail]  [44.154.1.3]  %
% E-mail  : [e-mail]                %
%           [e-mail]        %
% Mail    : George Katsimaglis                    %
%           OITYLOY 13                            %
%           GR11523 ATHENS                        %
%           GREECE                                %
% Phone   : [phone]                        %
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

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

Date: 30 May 1992 09:13:18 -0700
From: [e-mail]
Subject: Packet BBS distributions
To: [e-mail]

The ALLUS/ALLCA, etc type of distribution scheme is also used here in
Northern California and has been for many years.  The rationale for
this goes like this:

1) All packet BBS should carry the same bulletins.  This prevents BBS
   DXing.  Many years ago, it was common for a person to check into 5
   or 6 BBS to see if there was an interesting bulletin to read that
   was not forwarded to the local BBS.  By having everyone carry the
   same bulletins, a user need only check his local BBS.

2) Everybody sending bulletins wanted their own distribution code.
   @RACES, @AMSAT, @DX, @CHESS, @ARES, @ARRL, @TAPR, @nauseam.  It was
   felt that the @xxxx should indicate the geographical area of
   interest rather than the subject.  Why is KEPS@AMSAT and KEPS@ARRL
   different?  Who cares which organization created the bulletin?
   Won't the same people who read KEPS@AMSAT want KEPS@ARRL?

That was thinking.  I think it was valid at the time and I haven't
seen anything to change that.  Other comments?

Roy, AA4RE

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

Date: 30 May 1992 06:15:27 -0700
From: [e-mail]
Subject: Rejected posting to I-PACRAD@UIUCVMD
To: [e-mail]

Your message is being returned to you unprocessed because it seems to have been
already sent to the I-PACRAD list. That  is, a message with identical body (but
possibly different headers) has been posted to the list recently, either by you
or by  someone else. If you  have a good reason  to resend this message  to the
list (for instance because half of the outbound spool files were lost in a disk
crash at  some intermediate node),  please alter the  message text in  some way
before resending  it. Note that  altering the  "Subject:" line or  adding blank
lines at the top or bottom of the message is not sufficient; you should instead
add a line  at the top explaining  why you are re-sending the  message, for the
benefit of the list membership.

------------------------ Rejected message (125 lines) -------------------------
Received: from CUNYVM.BITNET by VMD.CSO.UIUC.EDU (Mailer R2.07) with BSMTP id
 2066; Sat, 30 May 92 08:14:19 CDT
Received: from CUNYVM by CUNYVM.BITNET (Mailer R2.08) with BSMTP id 2281; Sat,
 30 May 92 09:12:46 EDT
Received: from ucsd.edu by CUNYVM.CUNY.EDU (IBM VM SMTP V2R2) with TCP;
   Sat, 30 May 92 09:12:45 EDT
Received: by ucsd.edu; id AA04796
    sendmail 5.64/UCSD-2.2-sun
    Sat, 30 May 92 04:30:06 -0700 for
 claris!voder!nsc!gpo.nsc.com!sinclair%spi.dnet
Received: by ucsd.edu; id AA04791
    sendmail 5.64/UCSD-2.2-sun
    Sat, 30 May 92 04:30:05 -0700 for /usr/lib/sendmail -oc -odb
 -oQ/var/spool/lqueue -oi -fpacket-radio-relay packet-radio-list
Message-Id: <[e-mail]>
Date: Sat, 30 May 92 04:30:04 PDT
From: Packet-Radio Mailing List and Newsgroup <[e-mail]>
Errors-To: [e-mail]
Reply-To: [e-mail]
Precedence: Bulk
Subject: Packet-Radio Digest V92 #145
To: [e-mail]


Packet-Radio Digest         Sat, 30 May 92       Volume 92 : Issue 145

Today's Topics:
               Packet BBS distributions
                 uo22
           UO22 uplink freqs? (help please)

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: 29 May 1992 20:46:59 GMT
From: ucsd.edu![e-mail]
Subject: Packet BBS distributions
To: [e-mail]

When ham packet BBS messages are sent, they are usually addressed to a
general subject area and a general distribution.  E.g., the send line is
something like

    SB  KEPS @ AMSAT

where the subject area (a primitive equivalent to a Usenet newsgroup) is
"KEPS", and the distribution is "AMSAT".

Presumably BBSs will have forwarding lists that can be set to forward
messages addressed to the distribution "AMSAT" to only those BBSs that
want to see it.  Of course, it is likely that the majority of these
BBSs will forward all but a few such distributions to their neighbors;
for example, I forward everything except a SDIEGO distribution to my
neighbor BBS in Los Angeles.

However, some time in the past, it seems that an agreement was reached
among a lot of the Southern California BBS Sysops that there were too
many of these distribution designators, thus causing confusion and a
maintenance problem for sysops.  These sysops decided they would only
forward a very few such distributions: ALLUS, ALLCA, ALLCAS, and a
city and/or countywide one.  All articles ("bulletins") entering one of
those BBSs would have its distribution address field REWRITTEN to one of
the acceptable few.

This strikes me as a particularly short-sighted decision.  However, not
being familiar with early BBS software, it may have been a convenient
method to simplify the maintenance of routing when dealing with stupid
software.

The AA4RE BBS package (with which I am most familiar, of the various
offerings) allows one to specify that distributions like "AMSAT" can
be TREATED as e.g., "ALLUS", without rewriting the field in the address.
Then the message can be distributed with much finer detail than can
currently done: for example, a DXers' BBS can ask its neighbors not to
feed it stuff from AMSAT.

This, to me, makes much more sense than rewriting the actual address.

Thus I think it's time for the people in my area to rethink their
current addressing scheme, particularly the rewriting addresses part.

Comments?
    - Brian

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

Date: Fri, 29 May 92 21:20:16 WIB
From: "Robby Soebiakto" <[e-mail]>
Subject: uo22
To: owpurbo@sunee

Onno, this may look strange, but i need the uplink freqs of UO-22. Could you
get the info from your sources? I discarded my @ AMSAT bulletins, and now i
need it! Thanks for helping me. Rob

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

Date: Fri, 29 May 1992 14:36:14 GMT
From:
 sdd.hp.com!cs.utexas.edu!utgpu!torn.onet.on.ca!watserv1!norton.waterloo.edu!owp
 [e-mail]
Subject: UO22 uplink freqs? (help please)
To: [e-mail]

I just received an inquiry from my friend Robby YB1BG in Jakarta
on the uplink freqs of UO22. We would greatly appreciate any info.
Attach is his original mail. Thanks.
73 Onno YC1DAV/VE3
    [e-mail]

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

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

End of Packet-Radio Digest V92 #145
******************************

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

End of Packet-Radio Digest V92 #146
******************************