Hi Tree -- I too found myself going back to the packet screen to find out
that Rusty was the one who'd posted a 10m mult I didn't have a prayer of
hearing down here in Santa Monica. When you get a moment (like in April)
change the prompt to include the dxpacketclusterposter's callsign. Thanks
& have a nice time in LA.
Randy Powell W6SW
P.S. Maybe by April I'll know my callsign.
----------
> From: D. R. Evans <devans@lynx.colorado.edu>
> To: trlog@contesting.com
> Subject: RE: + request
> This was the first time I'd used packet with TR. Boy, that band map is
> great. Now I just need to replace my aging 930 (or convince my clever
> brother to come through with his promise to make me a computer interface
> for the thing). I did think that spots aged off the screen too quickly.
> Several times I had to go to the packet window and do a sh/dx/20 20 (or
> whatever) to get back a bunch of still-valid spots.
>
> How about if instead of "Packet says" it would say "WB0ABC says"??
>
> The reason for asking for this is the following:
> The operators at K0RF frequently posted spots that were either a)
> inaudible to ordinary mortals; or b) stations worked on K0RF's run
> frequency (!)
>
> For this reason, I frequently found myself forced to go to the packet
> window and see who had posted a spot before toddling off to try to work
> it. If K0RF was the source, I generally ignored the spot, since it was
> often a waste of time to go looking for it.
>
> And I LOVE the new custom characters.
>
> --------------------------------------------------------
> D.R. Evans N7DR / G4AMJ : devans@lynx.colorado.edu
> Member, 1997 Nebula Novel Jury al019@freenet.uchsc.edu
>
> "Palindor Chronicles" information and extracts:
> http://spot.colorado.edu/~romigj/drevans.html
> --------------------------------------------------------
>
|