HDTenEightyP/NetNews huggingface dataset:
From: bobw@col.hp.com (Bob Witte)
Subject: Re: ARRL RPTR Directory Stinks :-( (?)
Date: Mon, 12 Oct 1992 22:48:12 GMT
Organization: HP Colorado Springs Division

sknapp@iastate.edu (Steven M. Knapp) writes:
  [stuff Deleted ] 
> THE REAL SCAM is that is costs $$ to be in it as well as to buy it. While I
> will agree that the ARRL is all we have lobbying for us in congress, they
> could do a better job with a few things....
>
   What? My UHF machine is in the directory and I am sure that 
   I didn't pay any money for that.

   Bob KB0CY
   bobw@col.hp.com
From: William=E.=Newkirk%Pubs%GenAv.Mlb@ns14.cca.CR.rockwell.COM
Newsgroups: rec.radio.amateur.policy
Subject: CW Recertification
Date: 16 Oct 1992 10:54:53 -0700
Organization: UCSD Usenet Gateway
NNTP-Posting-Host: ucsd.edu

>Yeah, right. The only place that the FCC is running out of calls, particularly
>in California is in the Novice/Tech/General group. I believe the last
>2x1 Extra calls have gone, but they have plenty of calls to give out to
>Advanced and Extra, particularly when you consider the rate that these
>licenses are granted versus the Tech range.

?? 

4-land is ahead of 6-land in 2X3's assigned, last i looked.  and just the K's 
alone make up a block of calls about 456K in size...given that there are 
around 600K hams in the entire US, i would doubt that 6-land is "running out" 
of calls - unless every is just playing "call sign lotto" and filing lots of 
"change call sign" requests...(possible civil disobediance project??)

the fourth call district is out of group A (2x1, 1x2) and C (1x3) calls.

of course there are some of the K 2x3s that are reserved but of course once 
these are used then you can proceed to the Nx#xxx... lots of possible calls 
still exist before things even begin to get tight.  I don't know if i would 
want NZ#ZZZ tho....

bill wb9ivr
Newsgroups: rec.radio.amateur.policy,rec.radio.amateur.misc,rec.radio.amateur.packet
From: sknapp@iastate.edu (Steven M. Knapp)
Subject: Re: ARRL RPTR Directory Stinks :-( (?)
Organization: Iowa State University, Ames, IA
Date: Mon, 12 Oct 1992 03:42:37 GMT

In article <BvxH9H.Crn@zero.com> steve@zero.com (Steve Urich) writes:
>In article <1992Oct9.022433.7423@col.hp.com> bobw@col.hp.com (Bob Witte) writes:
>	I think they should drop it if they can't handle it. Then again they
>	should get rid of the beacon list and all of the other non repeater
>	info. But why don't they do this? Because it would make the publication
>	smaller and then they can't sell it for $6.00 therefore they would
>	not be making the profit by selling a directory that hardly changed
>	at all since the last directory. Imagine if they had only the repeater
>	info in there I would only buy a book once and never buy it again
>	because it wouldn't be worth buying since it didn't change much in
>	4 or 5 years get it? Its all a ARRL scam to produce a half-assed
>	directory with other bells and whistles with pages then last years
>	so it looks like things are happening for the advertisers. Too bad
>	the info is so outdated and wrong because it can't keep up with
>	the new technology out there. I'll never buy an repeater directory
>	again from ARRL until they catch up with the responsabilities.


THE REAL SCAM is that is costs $$ to be in it as well as to buy it. While I
will agree that the ARRL is all we have lobbying for us in congress, they
could do a better job with a few things....

For those with the '92 (blue) directory make this addition to the IOWA pages
under central:

Ames	WA0KHF	147.375	+	CARC 	oae

And if you are near Ames, give us a shout!


________________________________________________________________________ 
Steven M. Knapp		                    Computer Engineering Student
sknapp@iastate.edu	            President Cyclone Amateur Radio Club
Iowa State University; Ames, IA           Durham Center Operations Staff
Newsgroups: rec.radio.amateur.policy
From: willis@cs.tamu.edu (Willis Marti)
Subject: Re: ARRL DIGITAL COMMITTE REVISED REPORT 9/26/92
Organization: Computer Science Dept., Texas A&M University
Date: Fri, 9 Oct 1992 19:47:40 GMT

I have two problems with the Digital Committee's new report, one minor,
one major.

The minor one is that in their Appendix B they forget that unattended
digital stations exist above 10M. (The intent is clear from other paragraphs,
but it's not stated in this Appendix, which purports to cover "... all stations
under automatic control be restricted to the following Sub-bands...").

The MAJOR complaint is that someone has decided to remove some privileges
from Technician class licenses (I guess one understands packet better if the
code speed is >= 13wpm).

Quoted from the Report:
"97.216 Unattended Digital Station
 
(a) Any amateur station licensed to a holder of a General, Advanced or 
Amateur Extra Class license may be an unattended digital station."

What a load of hooey!  I'd like WA0CQG, Carl Estey, to present any
resaonable rationale for this line.

Willis Marti
N5SZF
Newsgroups: rec.radio.amateur.policy,rec.radio.amateur.misc,rec.radio.amateur.packet
From: bobw@col.hp.com (Bob Witte)
Subject: Re: ARRL RPTR Directory Stinks :-( (?)
Date: Fri, 9 Oct 1992 02:24:33 GMT
Organization: HP Colorado Springs Division

btbg1194@uxa.cso.uiuc.edu (Bradley T Banko) writes:
> As easy as it is to put up a packet BBS or such, I don't blame the ARRL
> or frequency coordinators for not wanting to track the changes there.
> I don't have any idea about how much staff the ARRL has for this stuff,
> but I think that the repeater directory is a fine, first-order approximation
> to repeater frequencies for those who are travelling.
> Once you get one or two frequencies in an area, the hams can point you to
> other repeaters.
>
   It seems to me that the packet stuff is evolving and changing so fast
   that the ARRL ought to just drop it from the repeater directory.
   It seems like a bit of a mismatch anyway ('course, then there's the
   listing of Beacons!! Sheesh.)

> Maybe some packeteers should start collecting information on packet
> BBS's and frequencies for a new publication?  One that could cater to
> the special aspects of packet networking.
>
   The local BBS's in my area always seem to have files full of this
   kind of info.
 
 Bob Witte  /  HP Colo Springs  /  bobw@col.hp.com   /  KB0CY
From: steve@zero.com (Steve Urich)
Newsgroups: rec.radio.amateur.packet
Subject: Re: Kantronics KPC-1?
Date: 13 Oct 92 17:45:05 GMT
Organization: Beyonet - Zero Network

In article <14580038@hpnmdla.sr.hp.com> alanb@hpnmdla.sr.hp.com (Alan Bloom) writes:
[...]
>I did some experimenting, and found that the KPC-2 occasionally locks 
>in transmit when power is first turned on.  Evidently there was a 
>momentary power failure when I was not at home.

	This has happened to 2 AEA users that I know of. There was a power
	clitch in our area one day and the next thing I noticed was a carrier
	on the freq that I use. The unit was a PK-88 and it was stuck in
	limbo with a nasty two tone squeal. I suspect it was something
	to do with the code beacon part of the firmware.
	If there was a timer in this box then their must have been a bug 
	because it was locked for over 8 hours. Lucky it wasn't a 50w radio
	but just an HT that went thru the ordeal with just a warm chassis :-).

	The other guy that I tracked down had a AEA PK-232mbx, that was just
	throwing a carrier. When I got a hold of the owner after approx 6 hours
	he told me his tnc was not showing that it was transmitting but the
	radio was still locked in transmit. He believed it was a bad mic plug.
	Remember those mic plugs that have a high resistance inbetween the 
	bakalite(sp?) substance after they get used for a while. I think that
	due to bad manufacturing processes that dope it with impure materials.

>I had always assumed that there WAS a timer in the box.  All the other
>TNC's have them.  Why doesn't Kantronics include a warning in the manual?

	Same here, maybe they don't work as well as they should in strange
	situations like power glitches...

	Steve
-- 
|Stephen Urich|        Internet:steve@zero.com         | "Cattle mutilations  |
|NIC: SU2     |   UUCP:beyonet!steve@cs.widener.edu    | are up!" --Sneakers  |
|ARS: WB3FTP  |  Packet:WB3FTP@WA3NWL.#EPA.PA.USA.NA   | ax25<->PBBS<->IPGATE |
|Bensalem, PA |Radio:wb3ftp@wb3ftp.ampr.org[44.80.8.44]| TCP/IP-FTP-SMTP-UNIX |
Newsgroups: rec.radio.amateur.packet
From: jvp@vlsi2.ee.iastate.edu (Jim Van Peursem)
Subject: Re: PK232 programs
Keywords: PK232 Packet Programs
Organization: Iowa State University, Ames IA
Distribution: usa
Date: Thu, 15 Oct 1992 16:14:57 GMT

In <1992Oct14.144309.10170@merlin.hgc.edu> jens4813@hgc.edu (Kevin Jensen) writes:

>Does anyone have any suggestions on what is available for programs
>that are freeware or shareware to control the PK232? I also need 
>the unarchiving utility if you suggest something on a ftp site
>on the internet. I used archie and found PK232.ARC and PK232COM.ARC
>but I didnt look any farther with archie. Are these programs any good?
>What is the unarchiving program I should use to unarc these? Thanks
>for any replies.

For what computer?

-Jim

Xref: sparky rec.radio.amateur.packet:2738 rec.radio.amateur.misc:17197
From: rnielsen@tapr.ampr.ORG (Bob Nielsen)
Newsgroups: rec.radio.amateur.packet
Subject: PSK on 10 meters
Date: 12 Oct 1992 08:19:26 -0700
Organization: Tucson Amateur Packet Radio
NNTP-Posting-Host: ucsd.edu

In Packet-Radio Digest #276, rsavage writes:
>Have people tried using 1200 baud BPSK modems on 10 meters?

There were some articles on this in the May and September issues of QEX, 
reprinted in the October 1991 issue of Packet Status Register.  The 
authors (W9UWE, KB6BT and K2RDX) report excellent performance as well as 
monitoring operation from Japan, Philippines and Australia on 15 meters, 
where 1200 baud operation is legel on that band.

He further suggests 9600 bps operation on 6 meters.  In much of the 
western US, there is a 4800 bps backbone which has been in operation for 
several years on this band.


+++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+ Bob Nielsen W6SWE    Internet: rnielsen@tapr.ampr.org +
+                      ax.25: w6swe@wb7tpy.az.usa.na    +
+ Tucson, Arizona      amateur IP: 44.124.12.16         +
+                      CIS: 71540,2364                  +
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Newsgroups: rec.radio.amateur.packet
From: wa2ise@cbnewsb.cb.att.com (robert.f.casey)
Subject: Re: Kantronics KPC-1?
Organization: AT&T
Distribution: na
Date: Tue, 13 Oct 1992 02:46:26 GMT

In article <14580038@hpnmdla.sr.hp.com> alanb@hpnmdla.sr.hp.com (Alan Bloom) writes:
>I did.  My !@#$%^&! KPC-2 locked up in transmit -- it was over a day 
>before I noticed.  Fortunately the power supply failed first and acted
>as an (expensive) fuse for the radio.  
>
>I did some experimenting, and found that the KPC-2 occasionally locks 
>in transmit when power is first turned on.  Evidently there was a 
>momentary power failure when I was not at home.

My KPC2 _once_ got stuck in transmit mode for a day or so.  In my case, the
radio took it OK, and so did the power supply.  This probably wiped out
activity on the freq in my area.  But I only run 8 watts (about half gets
out of the 50 feet of RG58).  Haven't had it happen again for a couple 
years.
From: Angelo_Glorioso_Iii@agwbbs.new-orleans.LA.US (Angelo Glorioso Iii)
Newsgroups: rec.radio.amateur.packet
Subject: Re: G8BPQ 6.0
Distribution: world
Date: 8 Oct 92 22:19:40 CST
Organization: The Amiga GateWay BBS * New Orleans, La.

Thanks for the update..

Angelo


-- Via DLG Pro v0.992

Internet:angelo_glorioso_III@agwbbs.new-orleans.LA.US
  Usenet:rex!agwbbs!angelo_glorioso_III
  Packet:N5UXT @ N5UXT.#NOLA.LA.USA.NA
  Tcp/ip:N5UXT.AMPT.ORG  [44.108.2.13]
Newsgroups: rec.radio.amateur.packet
From: sbrown@charon.dseg.ti.com (Steve Brown)
Subject: Ham TCP/IP address
Organization: /usr/people/sbrown/.organization
Distribution: usa
Date: Wed, 14 Oct 1992 12:49:37 GMT

Hi,

I'm just getting started in packet radio and need someone to point me
in the right direction to get a ham TCP/IP address.  The only info
I have thusfar is a name and call in "Gateway to Packet Radio."  Seems 
this should be an appropriate forum for this question.

Thanks,

Steve, WD5HCY
sbrown@charon.dseg.ti.com
--
               *******************************************
               |  Steve Brown, WD5HCY       | Simplicate |
               |  vax1::sbrown              | and add    |
               |  sbrown@charon.dseg.ti.com | lightness. |
               |  (214) 575-3597            |            |
               |  MSG:SBRN                  |    - Bill  |
               |  MS 8496, PSK0             |      Stout |
               *******************************************
From: john@goshawk.mcc.ac.uk (John Heaton)
Newsgroups: rec.radio.amateur.packet
Subject: Re: AmigaNOS 2.9g help needed.
Date: 8 Oct 92 11:13:17 GMT
Reply-To: john@nessie.mcc.ac.uk
Organization: Manchester Computing Centre

In article <9210051936.AA24084@ucsd.edu>, MUSCHINSKE%39A.DEcnet@scfb.nwc.navy.mil (39A::MUSCHINSKE) writes:
|> Hello,
|> 
|> Has anybody come up with a documentation set for AmigaNOS yet?

I haven't had time to write the documentation as such, but most of it is
contained in the help files in tcpip;spool/help/...

|> 
|> Does anyone know the fix to stop monitored information packets in the
|> trace mode from overwriting the previously printed line?

When in 'the trace mode' do you use trace output to a separate window? or
just the same window that AmigaNOS was started from?.

|> 
|> 73, Erich
|> 
|> AX.25:   KA6AMD @ WA6YBN.#SOCA.CA.USA.NA
|> Internet:  muschinske%39a.decnet@sunman.chinalake.navy.mil
Newsgroups: rec.radio.amateur.packet
From: brit@athena.MIT.EDU (Christopher B Gould)
Subject: No more BayCom modem trouble
Organization: Massachusetts Institute of Technology
Date: Wed, 14 Oct 1992 23:26:34 GMT

Thanks to all ye who helped me out with the BayCom questions I posted!

Apparently I got a hold of an old copy of the schematics for the TCM3105 modem.
There was a small error which was corrected about a year or two ago, but it seems
there are still old versions hanging around the net.

I must say it's very nice when the authors send helping email right after I posted
the questions.

Congratulations to the BayCom team!

73, Brit

KB4ZBP (soon to find a packet mail address)
brit@athena.mit.edu
From: makinc@hhcs.gov.au (Carl Makin)
Newsgroups: rec.radio.amateur.packet
Subject: Re: Packet-Radio Digest V92 #267
Date: 7 Oct 92 16:07:13 +1000
Organization: Aust. Dept. Health, Housing and Community Services

In article <T2uZRB1w164w@phsbbs.princeton.nj.us>, n2gj@phsbbs.PRinceton.nj.US (Gerry Jurrens) writes:

> acknowledgement in the form of "RCVD #nnnn...." and AEA says it should 
> only be sending me "F>" and nothing else.  AEA says "Tell the sysop to 
> suppress that message."  KB1BD says "No can do.  No one else has this 
> problem..."  

Is this the ROSE PRMBS?  I've never used it however it sounds
like the sysop of the PRMBS needs to define you to his box as a
'BBS'.  That should stop extranious messages.

Carl.

-- 
Carl Makin, MVS/ESA Systems Programmer, VAX/VMS Dabbler. 
Dept. Health, Housing and Community Services, Canberra, Australia.
sserve.cc.adfa.oz.au!hhcs!makinc   -   UUCP
makinc@hhcs.gov.au		   -   Internet
vk1kcm@vk1kcm.act.aus.oc	   -   Packet Radio
"I'm from the Government and I'm here to help you."
From: ssuhouns@csug.cs.reading.ac.uk (Paul Marshall Hounslow)
Newsgroups: rec.radio.amateur.packet
Subject: Re: PktWin V1.0 TNC controller for Windows
Date: 15 Oct 92 12:23:48 GMT
Reply-To: ssuhouns@csug.cs.reading.ac.uk
Organization: Dept. of Comp. Sci., University of Reading

In article 3714@eng.umd.edu, chuck@eng.umd.edu (Chuck Harris - WA3UQV) writes:
>In article <Bw446o.Gz0@csug.cs.reading.ac.uk> ssuhouns@csug.cs.reading.ac.uk writes:
>....
>>     I have uploaded PktWin to ftp.cica.indiana.edu.  It is 
>>currently in /pub/pc/win3/uploads as PKTWIN01.ZIP.
>>
>>It is an Amateur Radio Packet TNC controller program, and is
>>shareware (25 pounds registration). 
>>
>Thank you Paul.  Now, what does it do?  What features does it implement?
>Whose TNC will it work with?  What modes does it support?  What computer
>does it run on?  Please don't assume that we already know.
>
>Enquiring minds want to know!
>
Weeelllllllllllll.

It is TNC controller program for Windows 3.1 (IBM PC).
It is quite basic, so it should support most TNC's, I have tried it
with PK-88 and Tiny-2 type TNC's, doesn't use KISS mode or any other fancy
'host' mode controller protocols.  I does support text transfer, YAPP will
be coming (I hope ;-) in a future version, I have the source (in Pascal :-(
but am a bit busy just at the moment.  It supports normal windows stuff, such
as cut and paste with the clipboard.  There are two text buffers, one for
receive and one for transmit, either can be from 1k to 1024K bytes (tho.
pointless for TX ;-)  and lots more ;-)



Paul

----
73's de Paul                         The smelling pistakes are all my own.
Packet: G4YFY@GB7BEQ                 I have no employer (I retired ;-).
EMail:  ssuhouns@susssys1.rdg.ac.uk  1990 16 valve K100LT        DoD #0573
From: rnielsen@tapr.ampr.ORG (Bob Nielsen)
Newsgroups: rec.radio.amateur.packet
Subject: TAPR
Date: 12 Oct 1992 08:33:40 -0700
Organization: Tucson Amateur Packet Radio
NNTP-Posting-Host: ucsd.edu

In packet-radio digest #277, gerry K8EF writes,

>Have you a source for "Packet Shift Register"; maybe address for TAPR?

The name of the newsletter is "Packet Status Register".  TAPR can be 
reached at:

Tucson Amateur Packet Radio
P.O. Box 12925
Tucson, AZ 85732

Phone 602-749-9479
(Office hours 10am - 3 pm, Tues-Fri)
FAX 602-749-5636

Internet:  tapr@tapr.ampr.org

Bob Nielsen, W6SWE
President, Tucson Amateur Packet Radio

+++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+ Bob Nielsen W6SWE    Internet: rnielsen@tapr.ampr.org +
+                      ax.25: w6swe@wb7tpy.az.usa.na    +
+ Tucson, Arizona      amateur IP: 44.124.12.16         +
+                      CIS: 71540,2364                  +
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Newsgroups: rec.radio.amateur.packet
From: plumer@boreas.Stanford.EDU (Edward S. Plumer)
Subject: KPC-3 power jack
Organization: Stanford University, California, USA
Distribution: usa
Date: Tue, 13 Oct 92 05:04:04 GMT


I just bought a Kantronics KPC-3 and tried to do
the battery mod.  I discovered that the external
power jack was defective and when the external
power plug was not attached, the 9V battery
was not connected.... This happened on two
successive TNC's!  Kantronics promises to
send me a new working jack.  If anyone has
similar problems, they might call Kantronics
tech support.  I would be curious to know
if anyone has successfully done the modification
or if all units have defective power jacks.

Edward (KM6IQ)
plumer@isl.stanford.edu

Newsgroups: rec.radio.amateur.packet
From: bad1679@ultb.isc.rit.edu (B.A. Doehner)
Subject: tcp/ip configuration
Originator: bad1679@ultb
Reply-To: bad1679@ultb.rit.edu (bernie doehner nu1s)
Organization: Rochester Institute of Technology
Distribution: usa
Date: Tue, 13 Oct 1992 01:49:51 GMT


Hi all,  
I currently have my Amiga 500 configured as a host on our local Packet
Radio Tcp/ip network.  Next quarter, a friend of mine also with an Amiga
500 will be moving in next door.  Since I have two working serial ports,
I would like to have one line running slip to my neighbours Amiga500
for remote file access and the other line connected to the tnc and two
meter radio.

My friend is not licensed as an Amateur Radio Operator so I am a little
bit worried about keeping isolating his host from other ip users on
our packet network.  How can I configure my host to prohibit gatewaying
across my machine?
      __________________   slip  ______________     _____  _________
      | friend.ampr.org |--------|nu1s.ampr.org|----|tnc|--|vhf rig|
     -------------------         --------------      ---    ------- 

Thanks for any pointers..

Bernie nu1s@nu1s.ampr.org [44.69.0.37]
-- 
Electrical Engineering, Rochester Institute of Technology, Rochester,NY
Ax25 Packet: NU1S @ WB2PSI.#WNY.NY.USA.NOAM  (normal packet route) 
Internet (school): bad1679@ultb.isc.rit.edu
From: tstader@aol.COM
Newsgroups: rec.radio.amateur.packet
Subject: NET/Mac(2.3.9) questions
Date: 16 Oct 92 06:25:31 GMT
Article-I.D.: aol.9210161612.tn25819
Organization: UCSD Usenet Gateway
NNTP-Posting-Host: ucsd.edu

Has anyone ever been able to really figure out what causes the backoff timer
to kick in during an ftp session?

The reason I ask this question is that during an extensive series of ftp
sessions across several local lans I discovered some interesting anomolties.

Currently have tcp settings of:

tcp mss 216
tcp window 432
tcp irtt 5000

hopefully to reduce the overhead of oustanding packets, etc>

After establishing a couple of ftp sessions with a single station which is
also a Mac. I started the xfer process and everything seemed to be going OK.
File sizes were 169K and and 91K using type i and macbinary enabled. They
were StuffIt archives.

After while I did a check of the status with the "t e #" command and not too
much of either file was xfered. I left the station go at it overnight and the
next morning the files were only about half done! Came back after work (9
hours later) and the files were about 3/4 complete. 

I decided to look at the activity on frequency with the trace ax0 111 command
and it didn't look too bad. So I decided to kick the sessions for awhile and
things got moving again. I came back in about 2 hours and both files were
finished!

So I guess I have to ask this question..... does having the trace mode on in
an active window have anything with the operation? The channel activity
seemed to be about the same during the period. Sure is suspicious?

Another thing I don't understand ise routing statements. I put a couple of
statements in to bypass our local switch and go to another station who has a
very good path to another Mac station. I placed in my autoexec.net the
following lines to cover this

route add [44.56.a.a] ax0 
#for the station who I need to go to access this other station

route add [44.56.b.b] ax0 [44.56.a.a]
#this line to cover the routing to the station I want to talk to

If I ping station "b" it goes to the switch! If I ping station "a", it
bypasses the switch and goes to him directly!

Now if I add these lines in manually from the console window, substituting
their ax.25 calls instead off their IP addresses... it works the way I would
expect. What did I do wrong?

Any help here would be greatly appreciated.

73 for now.... c u on the shortwaves
Terry - KA8SCP/1, America Online Ham Radio Club Host
Internet: tstader@aol.com (files <28K)  _or_  
          tstader@attmail.com (files >28K)
KA8SCP@WA1PHY.#EMA.MA.USA.NOAM  _or_ 
ka8scp@ka8scp.ampr.org [44.56.4.82]
From: alanb@hpnmdla.sr.hp.com (Alan Bloom)
Date: Mon, 12 Oct 1992 19:00:18 GMT
Subject: Re: Kantronics KPC-1?
Organization: Hewlett-Packard, Santa Rosa, CA
Newsgroups: rec.radio.amateur.packet

In rec.radio.amateur.packet, steve@matt.ksu.ksu.edu (Steve Schallehn) writes:

>davros@ccwf.cc.utexas.edu (Buddy Brannan) writes:

>As Gary said, the KPC-1 does not have a watchdog timer.  However, I
>have never had any trouble with my KPC-2 or my KAM keying up and
>burning out a radio.  Nor have any of the other 20 Kantronics users
>that I know.  (I think we have had this discussion before :-) )

I did.  My !@#$%^&! KPC-2 locked up in transmit -- it was over a day 
before I noticed.  Fortunately the power supply failed first and acted
as an (expensive) fuse for the radio.  

I did some experimenting, and found that the KPC-2 occasionally locks 
in transmit when power is first turned on.  Evidently there was a 
momentary power failure when I was not at home.

I had always assumed that there WAS a timer in the box.  All the other
TNC's have them.  Why doesn't Kantronics include a warning in the manual?

AL N1AL