[BC] corporate silliness

[DSmith2381 at aol.com]

I totally agree.......if you notify the FCC, they will  respond, and not 
only will the EAS hit the fan....the humus will hit the  oscillator, and 
probably spread it all over the corporate checkbook.  That  sounds like it could 
be fodder for license revocation...or a show cause hearing  if nothing else.
 
Don Smith
WCLN
Clinton, NC
 
In a message dated 6/1/2009 8:19:18 P.M. Eastern Daylight Time,  
Broadcast at fetrow.org writes:

I  STRONGLY suggest you report this to the FCC.  It is one of the few   
things they take seriously.

My cable company refused to let me see  the Public File.  My problem  
was their lack of EAS  compliance.  The woman who refused me access  
gave me a hand  written note that she had done that.

I had no luck getting the FCC to  go after them for EAS, but with the  
hand written refusal of access  to the Public File the FCC got  
interested.  I was able to get  them to inspect, and the EAS issues hit  
the  fan.

--chip

On Jun 1, 2009, at 6:46 PM,  broadcast-request at radiolists.net wrote:

> Message: 18
> From:  Barry Mishkind <barry at oldradio.com>
>
> Last week, I had a  friend describe to me the response he had when
> calling a local cluster  of a major group. He called before going to
> the stations as a courtesy  because he wanted to see a Public File:
>
>       The person answering the phones said "our files are
>   all private, and we do not show them to  anyone."
>
> He then asked for the name of the general  manager.
>
>         "That is private  personnel information."
>
> I can verify that in calling out for  information, more than once I've
> also been met with that they are not  allowed to give you the name of
> the GM, Chief Engineer, or other key  employees.
>
> It just makes your head shake a  bit.
>
> At 10:19 AM 6/1/2009, RichardBJohnson at comcast.net  wrote:
>> Sure. Somebody answered and said they'd have somebody  contact me.
>>
>> ----- Original Message -----
>>  From: "Barry Mishkind" <barry at oldradio.com>
>>
>> Just  a strange thought ... did you try calling the station on their
>>  phone  number?