From: steve@zero.com (Steve Urich)
Newsgroups: rec.radio.amateur.policy,rec.radio.amateur.misc,rec.radio.amateur.packet
Subject: ARRL RPTR Directory Stinks :-(
Summary: Who is in charge of this mess?!?!?
Keywords: Coordinators Editors
Date: 6 Oct 92 15:55:16 GMT
Organization: Beyonet - Zero Network


	I recently bought the latest edition (1992-1993) of The ARRL
	Repeater Directory since I have never owned one while being
	a ham for 15.5 years and only being a member of the ARRL for
	1 year (The first year From Feb 24, 1977 to Jan 31 1978).

	This book is a disgrace! :-( Someone is not doing their job
	in editing, registration of new updates, and coordination.

	There are so many errors that I am sorry I even bought it now.
	I would be ashamed to even have printed this if I knew what
	was in it. I mainly bought it for the Packet information but
	I now find that the Freq coordinators are the only ones allowed
	to submit an update for the packet section and most of them
	are ignoring any new updates. The freq coordinators don't want
	to get involved in packet updates period from what I have seen
	in the book and what I have heard. I recently send a bunch of
	TCPIP packet mail to a few listed fellow hams and here is 
	one of the replys that I got:

---Start smtp packet mail forwarded---

From wa3tsw.ampr.org!wa3tsw Wed Sep  9 21:33:24 1992
Return-Path: <wa3tsw.ampr.org!wa3tsw>
Received: by beyonet.zero.com (/\==/\ Smail3.1.21.1 #21.29)
	id <m0mSdPN-0001EcC@beyonet.zero.com>; Wed, 9 Sep 92 21:33 EDT
Received: from wa3dsp.ampr.org by wb3ftp.ampr.org with SMTP
	id AA104 ; Wed, 09 Sep 92 21:19:10 EST
Received: from wa3tsw.ampr.org by wa3dsp.ampr.org (NOS TCPIP BBS) with SMTP
	id AA16907 ; Wed, 09 Sep 92 21:05:19 GMT
Date: Thu, 10 Sep 92 00:40:10 GMT
Message-Id: <3533@wa3tsw.ampr.org>
From: wa3tsw@wa3tsw.ampr.org (John Robison)
To: wb3ftp%wb3ftp@wa3dsp.ampr.org
Subject: Re: ARRL RPT DIR Entry
Status: O


I consider the ARRL Repeater Directory to be a lost cause.  For three years
in a row I sent them current information but they refused to accept it.  They
only take input from the "frequency co-ordinators".  The frequency co-
ordinators don't have anything to do with packet.  They don't want the 
added burden of passing the information on to the ARRL for packet operation.
I was never able to get all of my entries correct.  It always got scrambled
along the way.  Even the one for my voice repeater on 440 is wrong.  I
decided I didn't need the aggravation and forgot about it.
I don't send updates anymore and I don't buy the book.  The last one I have
seen is the 1990/1991 issue.  A consciencious editor would have purged the
221.01 entries.  They don't seem to care whether it is accurate.  Only that
it is thick enough to fetch a good price.  I understand that this years
directory left out a whole area of Texas.  Thanks for caring but I no
longer do.  Life is too short; since my heart attack I don't let things like
that bother me anymore.

73, John


---End of Forward smtp mail---

	There you have it, quoting John: "This years directory left out a
	whole area of Texas." Well at least it was left out if it was 
	WRONG right?!?! Look at the packet listing for 220Mhz in Pennsylvania.
	They still have listings below 222Mhz. What is the Editor doing
	at ARRL, isn't that his job to make sure its ok? I believe the
	freq below 222Mhz are nolonger ham freq correct :-).

	Just wanted to let the net know about another "BUG" in the great
	ARRL, INC. :-) I'll take John advice and say "Life is too short
	and not let this bother me also". 

	73 and thanks for reading my post, I hope you've enjoyed it as
	much as I have typing it :-)
	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.policy,rec.radio.amateur.misc,rec.radio.amateur.packet