Message Area
Casually read the BBS message area using an easy to use interface. Messages are categorized exactly like they are on the BBS. You may post new messages or reply to existing messages!

You are not logged in. Login here for full access privileges.

Previous Message | Next Message | Back to Amateur Radio Interest  <--  <--- Return to Home Page
   Networked Database  Amateur Radio Interest   [798 / 900] RSS
 From   To   Subject   Date/Time 
Message   Daryl Stout    JIMMY ANDERSON   Re: My pet peeves   May 5, 2019
 12:48 PM *  

Jimmy,

JA>There's a local HAM that says "Roger Roger" pretty often, like someone
JA>saying "um" or "y'know" or any other verbal tic. He means nothing by
JA>it, it's just his way of acknowledgement before continuing on to his
JA>next statement.

  If you get into a net who has one or more hams named "Roger", and if
one ham says "Roger", the actual "Roger" may say "You called??" <G>. As
a note, N0RSR, Roger, from Casa Grande, Arizona, along with his XYL,
Trish (I forget her callsign offhand), check into the D-Star Trains Net
every so often. That net, plus the Food Net, and the QCWA D-Star Net,
are all moving from Reflector 26 to the QuadNet Array this month. There
was a story in the May 3, 2019 edition of Amateur Radio Newsline, on
this.

JA>LOL - yeah every now and again I'll hear some repeater talk where someone
JA>mentions getting a QSO. Doesn't bother me, but I notice it.

  I tell hams to not use 10 codes, and to save the Q-signals for the
digital modes. I do have a ham radio humor file of "The Missing Q
Signals", but some are not appropriate for ham radio <G>.

JA>The only time I've heard this myself is when the repeater gives it's
JA>callsign after 10 minutes and it's kind of a reminder that if you've
JA>been talking a while it's a smart thing to stay legal and give your
JA>sign. If one says "for ID" it will prompt and teach the other person
JA>the reason you're doing it. Yes, they should know, but if you're
JA>talking while driving home from work it's easy to lose track of time
JA>and if you happen to stay keyed up while the repeater does its thing
JA>then you might miss it completely. Hearing the other person do it
JA>and WHY is a good reminder.

  I use the "clock method". I identify at the top of the hour, then at
10, 20, 30, 40, and 50 after the hour. Then, I don't have to worry
whether or not it has been 10 minutes.

JA>LOL - I admit I don't always think to power down my 50watt mobile rig,
JA>but I might be talking to a repeater 60 miles away, and I'm always
JA>scanning repeaters as far as 100 miles away. Yes, I know I don't need
JA>the power to 'listen.' I also don't think my 50w mobile is what you're
JA>referring to either. ;-)

  All knobs to the right!! <BG>

Daryl, WX4QZ

===
 ■ OLX 1.53 ■ OK, so what's the speed of dark?
--- SBBSecho 3.07-Win32
 * Origin: FIDONet: The Thunderbolt BBS - tbolt.synchro.net (1:19/33)
  Show ANSI Codes | Hide BBCodes | Show Color Codes | Hide Encoding | Hide HTML Tags | Show Routing
Previous Message | Next Message | Back to Amateur Radio Interest  <--  <--- Return to Home Page

VADV-PHP
Execution Time: 0.081 seconds

If you experience any problems with this website or need help, contact the webmaster.
VADV-PHP Copyright © 2002-2024 Steve Winn, Aspect Technologies. All Rights Reserved.
Virtual Advanced Copyright © 1995-1997 Roland De Graaf.
v2.0.140505

Warning: Unknown: open(c:\Sessions\sess_9qa8hpim86ualn629r75igdhq5, O_RDWR) failed: No such file or directory (2) in Unknown on line 0 Warning: Unknown: Failed to write session data (files). Please verify that the current setting of session.save_path is correct (c:\Sessions) in Unknown on line 0 PHP Warning: session_start(): open(c:\Sessions\sess_9qa8hpim86ualn629r75igdhq5, O_RDWR) failed: No such file or directory (2) in D:\wc5\http\public\VADV\include\common.inc.php on line 45 PHP Warning: Unknown: open(c:\Sessions\sess_9qa8hpim86ualn629r75igdhq5, O_RDWR) failed: No such file or directory (2) in Unknown on line 0 PHP Warning: Unknown: Failed to write session data (files). Please verify that the current setting of session.save_path is correct (c:\Sessions) in Unknown on line 0