| |
ZL3AI > APRDIG 25.05.03 12:37l 307 Lines 9999 Bytes #999 (0) @ WW
BID : 1375-ZL3AI
Read: GUEST
Subj: TAPR Digest, May 22, 1/7
Path: DB0FHN<DB0RGB<OE5XBL<OE3XSR<OK0PBX<OK0PHK<OK0NAG<OK0PPL<DB0RES<ON0AR<
ZL2BAU<ZL3VML
Sent: 030524/1329Z @:ZL3VML.#80.NZL.OC #:858 [Chch-NZ] FBB7.00i $:1375-ZL3AI
From: ZL3AI@ZL3VML.#80.NZL.OC
To : APRDIG@WW
TAPR APRS Special Interest Group Digest for Thursday, May 22, 2003.
1. RE: WinAPRS/Precision Mapping 5.0
2. Re: Voice Alert on 144.39
3. Re: WinAprs/Precision Mapping 5.0
4. Now that Dayton is over...
5. Re: Voice Alert on 144.39
6. MCP-D7H and WinXP
7. Re: Throat Mic (Was: Install on BMW Motorcycle)
8. HA0DE-9 Emerg Beacon
9. RE: MCP-D7H and WinXP
10. Re: Voice Alert
11. Re: Voice Alert
12. Voice Alert
13. D7 going into NOCALL
14. Re: Voice Alert on 144.39
15. Re: Voice Alert on 144.39
16. Oops
17. Re: WinAprs/Precision Mapping 5.0
18. Re: Voice Alert on 144.39
19. Re: Voice Alert on 144.39
20. Re: Voice Alert on 144.39
21. Voice Alert 144.390 Cont'd
22. Re: APRS Install on BMW Motorcycle
23. APRS-NET COncept!
24. KPC3+ on a Balloon
25. Heart of The Black Hills of SouthDakota
26. Re: Voice Alert on 144.390
27. RE: APRS-NET COncept!
28. Area Objects test
29. Re: Voice Alert on 144.39
30. RE: APRS-NET COncept!
31. RE: APRS-NET COncept!
32. RE: APRS-NET COncept!
33. Ultra simple MIC-e repeater
34. RE: APRS-NET COncept!
35. RE: APRS-NET COncept!
36. RE: APRS-NET COncept!
37. Re: Ultra simple MIC-e repeater
38. Re: Ultra simple MIC-e repeater
39. RE: APRS-NET COncept!
40. "Gap Filler" digipeaters
41. Re: Ultra simple MIC-e repeater
42. RE: APRS-NET COncept!
43. RE: APRS-NET COncept!
44. RE: APRS-NET COncept!
45. Re: Ultra simple MIC-e repeater
46. RE: APRS-NET COncept! -- Radio Mirror
47. RE: APRS-NET COncept!
48. Re: "Gap Filler" digipeaters
49. Re: Ultra simple MIC-e repeater
50. Re: Ultra simple MIC-e repeater
51. Re: Ultra simple MIC-e repeater
52. Bogus Tropical Depression
53. Re: Ultra simple MIC-e repeater
54. RE: APRS-NET COncept!
55. RE: APRS-NET COncept! -- Radio Mirror
56. WinAPRS Crash
57. Re: D7 going into NOCALL
----------------------------------------------------------------------
Subject: RE: WinAPRS/Precision Mapping 5.0
From: "Herb Gerhardt" <hgerhardt@charter.net>
Date: Wed, 21 May 2003 21:17:14 -0700
X-Message-Number: 1
Yes, you need the new OCX file for PM 5. You can download it from:
http://www.tawg.org/
It is under the WinAPRS tab, then scroll down a little in that window. This
is my favorite download site for all APRS programs. A great site to
bookmark.
If you are running WinAPRS version 2.6.1 I would recommend you upgrade to
the latest version 2.7.2 which is the latest version and seems to run great
with no crashes.
Herb, KB7UVC
NW APRS Group, West Sound Coordinator
Our WEB Site: www.nwaprs.org
>-----Original Message-----
>
>What do I need to do in order to get this up and running? Download a
>different OCX?
>
>Thanks
>John/N0MEQ
----------------------------------------------------------------------
Subject: Re: Voice Alert on 144.39
From: Wes Johnston <wes@johnston.net>
Date: 22 May 2003 00:19:04 -0400
X-Message-Number: 2
On Wed, 2003-05-21 at 23:35, Herb Gerhardt wrote:
>Voice alert. Much ado about nothing!
wanna bet that this thread does more to raise people's awareness of
voice alert than Bob telling people about it for 2 years?
Wes
----------------------------------------------------------------------
Subject: Re: WinAprs/Precision Mapping 5.0
From: "Guy Story, KC5GOI" <kc5goi@tapr.org>
Date: Wed, 21 May 2003 23:20:49 -0500
X-Message-Number: 3
John, all you have to do is install PM 5.0 and register it by running the
Travler Program and following the directions. After that, run WinAPRS and
make sure to tell WinAPRS the drive letter of your cd. You can save
specific files if you duplicate the directory structure that is on the cd on
your hard drive. If you do that, there are some parameters in the program
and in WinAPRS. Hard drive access is much faster but does eat up hard drive
space.
73
Guy
----------------------------------------------------------------------
Subject: Now that Dayton is over...
From: Rich Garcia <k4gps@bellsouth.net>
Date: 22 May 2003 00:26:39 -0400
X-Message-Number: 4
Well now that Dayton is over I have not heard very much about it. Was
there anything new to speak of for APRS users ?
--
Rich Garcia K4GPS
Jupiter Farms FL.
www.richgarcia.net
Jupiter Farms Community Emergency Response Team
----------------------------------------------------------------------
Subject: Re: Voice Alert on 144.39
From: "Demetre Valaris" <sv1uy@sv1uy.ampr.org>
Date: Thu, 22 May 2003 08:15:26 +0300
X-Message-Number: 5
Hi all,
I have setup both my TH-D7 and TM-D700 on 100HZ VOICE ALERT mode on
144.800, the European APRS frequency, for a year now and I have not heard
anyone using it in Athens area yet. I have used the mode in 2 occasions
while driving in province areas of my country and I have never heard anyone
complaining. I usually have on my APRS STATUS text that I am QRV on RU1
(UHF REPEATER) when I drive around Athens and I have quite a few QSOS with
this setup on the UHF frequency. When I drive outside Athens, I change the
STATUS TEXT to QRV RU1/7088/14342.5KHZ according to what I want to do. I
have had quite a few QSOs that way but I still keep my VOICE ALERT setup
just incase anyone cannot operate on the frequencies I advertise!
I think VOICE ALERT does not do any harm if used sensibly by sensible
people. I think most radio hams are sensible. If you find a non sensible
one, well it is not the end of the world. If they cause intentional
interference they do not need VOICE ALERT to do so. If they cause
unintentional interference, one can ask them nicely to QSY.
VOICE ALERT sounds good to me and could have it's uses incase of an
emergency.
All the best!!!
===
73 de Demetre SV1UY
e-mail: sv1uy at sv1uy.ampr.org
PACKET MAIL: SV1UY@SV1UY.ATH.GRC.EURO
http://www.athnet.ampr.org/~sv1uy
----------------------------------------------------------------------
Subject: MCP-D7H and WinXP
From: "Mark Fellhauer" <sparkfel@qwest.net>
Date: Thu, 22 May 2003 00:22:38 -0500
X-Message-Number: 6
I've noticed there's a warning at:
http://www.kenwood.com/i/products/info/amateur/thd7a_7e_g_soft.html
about MCP-D7H software not working with WinXP.
Has anyone found a fix? I tried it with XP this evening and just got a
communications error every time I tried to access the HT.
I even set the program to run in Win98 compatibility mode with no success.
Any hints, suggestions, etc?
Works fine when I use the same computer booted into Win98, but that's a pain.
73,
Mark
KC7BXS
----------------------------------------------------------------------
Subject: Re: Throat Mic (Was: Install on BMW Motorcycle)
From: "Dakota Summerhawk" <dakotas@dotorg.org>
Date: Wed, 21 May 2003 23:34:30 -0600
X-Message-Number: 7
To bad the connection doesn't fit Kenwood, but I bet I can hack the cable
and use a Kenwood speaker mic cable to make it compatible.
Dakota
----------------------------------------------------------------------
Subject: HA0DE-9 Emerg Beacon
From: Rich Garcia <k4gps@bellsouth.net>
Date: 22 May 2003 07:28:41 -0400
X-Message-Number: 8
Anyone on the list that can get in touch with this person ? I have been
seeing beacons from them for the past 3 days.
Rich
--
Rich Garcia K4GPS
Jupiter Farms FL.
www.richgarcia.net
Jupiter Farms Community Emergency Response Team
----------------------------------------------------------------------
Subject: RE: MCP-D7H and WinXP
From: "AE5PL Lists" <HamLists@ametx.com>
Date: Thu, 22 May 2003 06:34:45 -0500
X-Message-Number: 9
I appologize, I posted this reply to the APRS HT SIG instead of this
SIG.
I take it you mean the MCP-D7G software? I am using version 1.1 without
problem on a fully updated Windows XP laptop. Having written a terminal
emulation program that works across all Win32 platforms, I can say that
the comm part shouldn't be a problem as basic serial I/O setup and use
hasn't changed since Windows 95 and Windows NT 3.5. Other things have
changed (like how a window is displayed), but not the basic serial
operation. Note that since XP is Windows NT based, direct access to I/O
ports such as how DOS programs use serial ports is not possible under
normal use.
That said, there are some things that might be tying up COM1 in Windows
XP that you might not expect. For instance, if your XP machine is
running an NVIDIA graphics adapter, some of their drivers are reported
to tie up COM1 for no reason (disable Nview 2.0). You might want to
check for other software that has COM1 open. If you have another COM
port, you might try it.
Hope this helps.
73,
Pete Loveall AE5PL
pete@ae5pl.net
----------------------------------------------------------------------
Subject: Re: Voice Alert
From: "Coe" <K4COE@hiwaay.net>
Date: Thu, 22 May 2003 07:39:14 -0500
X-Message-Number: 10
Admittedly I am coming into this discussion in the middle, but, it
seems that the Voice Alert concept pre-supposes that the user that
is the target of the alert is not using two or more radios and enjoys
the constant irritation of hearing the packet traffic in the
background. So if he doesn't, there will be repeated attempts for the
originating station to establish contact, along with the obligatory ID.
Oops, that message that I was trying to receive got talked-over and
now I am out of range and the xmit counter has been reached by
the sender. It also presupposes that the 'other' amateur is not
monitoring the frequencies designated for calling, 146.520 mhz.
Many persons riding in my vehicle get annoyed at the packet-in-the-
background distraction, so I don't have it turned up. Additionally,
when on the road with with my 200 and 70 cm dual band and 1100
cm CB operating, I am certainly not going to listen to the drone of
the packets in the background from my APRS-dedicated THD7A.
What about a specific APRS defined LOCAL ALERT packet that is
only processed as a 'heard direct' and never digipeated? Any
station hearing it would get the message.
Just a thought....
73
K4COE
Coe
Coe
K4COE@arrl.net
Hsv, Al
----------------------------------------------------------------------
Read previous mail | Read next mail
| |
