Don't pick on Coffman >> Gary Bashing!
Gary McDuffie Sr
Sorry for all the blank lines in this but my reader isn't allowing a
followup, saying I'm posting less than what I'm commenting on. This is
my fourth attempt!! Does anyone know a good cure?
dre...@icaen.uiowa.edu (Douglas J Renze) writes:
>Actually, for those who've been hammering on Gary, I'd advise that
>you take another look at his comment in light of the plethora of advice
>and wit he makes available on the net (yes, I'm serious, folks). I've
>posted many questions to the net, and in most cases, somewhere along the
>line I end up with an explanation from Gary which usually ends up among
>the clearest and most concise explanations I come across...including this
>particular question, which he responded to on the info-hams newslist where
>some kind soul cross-posted it for me...and which he later reposted to this
>group.
Please...no credit for someone else's very good deeds. I think you
might be refering to Gary Coffman, whom I'm not. Gary Coffman appears
to be one of the most knowledgeable gentleman on any of these groups,
and an all around nice guy to boot. Be careful who you are burning.
For those who continue to "Gary bash", I suggest you re-read the
followup post, since most of you misunderstood my original one. For
those who still want to hammer away, have at it. It won't bother me,
because I know what the original intent was and there was never
anything negative toward Doug. Can you say "water off a duck's back"?
========
>>Old hams helping new hams, Yea right. First of all, most of you
>>old hams don't even bother to respond to a call you don't know.
>>Do you have any idea how frustrating it is to call KB7YOU monitoring,
>>get no reply and then 30 seconds later hear one of you old farts jump
>>on and start talking to a fellow geriatric case? It happens way to
>>often for me to believe that you just happened to turn on your radio 20
>>seconds after I stop calling. Well, after having this happen lots
>>of times on repeaters and U/Vhf simplex, I decided to jump into HF.
>>
You are treating "monitoring" like a CQ. Monitoring means "I am here,
in case someone was looking for me". It doesn't mean I'm looking for
someone to talk to. I'm just letting my xyl or friends know that I'm
back in the vehicle in case they called while I was out.
>Ever tried joining a net? My first rig was a 2-meter handheld. The day
>I got my license, I ran inside and grabbed it, and called, "N0YVW listening."
>Nada. I was at it most of the day, and getting depressed. I went for a drive
>that night to get into some other repeater areas. Same thing. I was getting
>ready to come home, when on the repeater I happened to be monitoring, I heard,
>"QST all Linn County Hams for the CVARC Monday Night Net. This net meets
>every Monday Night at 8:30 on the CVARC 146.745/145 repeater. Net Control this
>evening is WB0ULO, Russ..." When it came time to log in to the net, I managed
>to squeak, "N0YWV...err, make that N0YVW, Doug, from Iowa City." And he
>came back to me! "Net recognizes N0YVW, Doug from Iowa City. That sounds
>like a pretty new call." He noticed!
> "Ticket just came in the mail today."
> "Well, then, welcome to Amateur Radio, Doug! I hope you enjoy it as
>much as I do!"
> That was a great welcome, as far as I'm concerned. Made up to me for
>what I got locally.
> Care to know some of my secrets for getting people to come back
>to me? Listen to them talk about their interests, what they do, whether
>they work on the repeater or are always putting up antennas. Then, when you
>have a question about their area of interest, give them a call! For example,
Right on, Doug! That's exactly how to do it.
>One local ham, KA0CNN, is an avid DXer, always going to antenna parties, and
>is involved with maintaining the local repeater. One day, I was soldering
>some coax connectors and just couldn't quite get it right. I heard him
>call, "KA0CNN mobile monitoring." So I came back with, "KA0CNN KA0CNN, this
>is N0YVW, do you have time to answer a quick question?" Yes, he did, he told
>me where to find the info I needed, and even offered to drop by a photocopy
>of it. I've done the same with other things--posted requests for info to the
>sunday and monday night nets and gotten answers back, come back with answers
>myself, etc. I've gotten good results. I'm still not on the "in" crowd,
>but people recognize my call and come back to me some, I come back to them
>and don't feel squeamish about it.
Sounds to me like you are doing much better than the average newcomer,
Doug.
=============
>>Gary, would you care to explain to me what is wrong with Dougs request
>>for help???
>The only thing I read into what he wrote about what's wrong with my request
>was an indictment of the system that makes you memorize all this kipple that
>can be looked up on a table for the exams (coax cable types, etc) rather than
>requiring you to learn *useful* things, such as operating procedure. Correct
>me if I'm wrong, Gary. Anyway, that can be read multiple ways, too--such as,
>"Look at what we've got when we have people willing to admit their ignorance
>so they can learn more!" :-)
Thanks, Doug. That's exactly how it was written and intended. It's the
system that's wrong, not you. Unfortunately, some of these guys have a
vivid imagination and a very itchy trigger finger. BTW, Doug, someone
said you were in NE?? Where? I'm in Scottsbluff, and you are welcome to
give me a call anytime.
Gary (McDuffie)
Andy Warner
In article <2ccn6i$g...@crcnis1.unl.edu>, mcdu...@unlinfo.unl.edu (Gary McDuffie Sr) writes:
> Sorry for all the blank lines in this but my reader isn't allowing a
> followup, saying I'm posting less than what I'm commenting on. This is
> my fourth attempt!! Does anyone know a good cure?
Delete some of the stuff you quoted. Just include enough to get
the gist across, we can always go back an read the original you
know..
Of course, I could just complain about any moron being able
to sit down in front of a newsreader, but I'll refrain :-)
> [lotsa quoted stuff deleted...]
--
andyw N0REN/G1XRL
an...@aspen.cray.com Andy Warner, Cray Research, Inc. (612) 683-5835