| |
ZL3AI > APRDIG 06.02.07 22:01l 252 Lines 9859 Bytes #999 (0) @ WW
BID : 9678-ZL3AI
Read: GUEST
Subj: [APRSSIG] Vol 32 #5, 2/3
Path: DB0FHN<DB0MRW<DK0WUE<I0TVL<TU5EX<F6KBI<F3KT<IW2OAZ<ZL2BAU
Sent: 070206/2051Z @:ZL2BAU.#79.NZL.OC #:31421 [Waimate] $:9678-ZL3AI
From: ZL3AI@ZL2BAU.#79.NZL.OC
To : APRDIG@WW
Message: 6
Date: Sun, 4 Feb 2007 16:10:26 -0500 (EST)
From: "Bob Bruninga " <bruninga_at_usna.edu>
Subject: Re: [aprssig] Good 30m Reference?
Regarding HF paths:
>Wouldn't GATE,WIDE2-1 be preferable? I'm assuming the
>vast majority of people who can put up decent fixed 30m
>antennas and gear should have no problem putting up a
>2m antenna that can hit a decent digi.
My thinking included a few minor thoughts...:
1) W1-1 is more universal than W2-1. So it improves the probability very
slightly.
2) W1-1 is a simpler concept that everyone can understand (1 hop) rather
than having to explain 2-1.
3) A W2-1 path arrives everwhere as a WIDE2-0 or WIDE2 and makes it
impossible to know that it was sent as a 1 hop packet or a 2 hop packet.
Too many people then will criticize the sender, even though he was only
sending 2-1.
Yes a 2-1 packet should arrive as a DIGI,WIDE2* packet showing it was one
hop, but it could have equally been a WIDE2-2 packet that went through 2
digipeater hops and only one digi identified itself, the other is an
old-WIDEn-N digipeter that is not current with the New-N Paradigm.
Bob, Wb4APR
------------------------------
Message: 7
Date: Sun, 04 Feb 2007 22:59:30 -0800
From: Mark Fellhauer <sparkfel_at_qwest.net>
Subject: [aprssig] Re: Windows US Daylight Time Change Screwup Looming
Mailing List" <aprssig_at_lists.tapr.org>
At 04:40 PM 2/3/2007, Stephen H. Smith wrote:
>Ever since Windows 95, Microsoft Windows has been able to automatically
>adjust the computer system clock for daylight time each spring and fall.
>
>Effective this year, U.S. Daylight Time will start 3 weeks earlier (1st
>week of March instead of beginning of April),. As a result, the automatic
>time change feature in Windows won't happen until 3 weeks after the
>fact. As a result, files will be time-stamped with an error of one hour
>for three weeks or more.
Let us not forget about all the embedded devices that automatically adjust
for DST. I predict that when this change happens elevators will plunge
passengers to their deaths, airplanes will fall from the sky, supertankers
will run aground and explode, phone, TV, and banking networks will
collapse, and people will riot. On the morning of Sunday, March 11, 2007
The worlds largest cities will be in flames and humanity as we know it will
end.
At least that's what the "experts" told us about the Y2K bug. I wonder if
those are the same experts who are now warning us about global warming?
Worse yet, the time on your KPC-3 will be wrong.
------------------------------
Message: 8
Date: Mon, 05 Feb 2007 06:40:04 -0500
From: Rich Mulvey <aprs_at_mulveyfamily.com>
Subject: Re: [aprssig] Re: Windows US Daylight Time Change Screwup Looming
Mark Fellhauer wrote:
>At 04:40 PM 2/3/2007, Stephen H. Smith wrote:
>
>>Ever since Windows 95, Microsoft Windows has been able to
>>automatically adjust the computer system clock for daylight time each
>>spring and fall.
>>
>>Effective this year, U.S. Daylight Time will start 3 weeks earlier
>>(1st week of March instead of beginning of April),. As a result, the
>>automatic time change feature in Windows won't happen until 3 weeks
>>after the fact. As a result, files will be time-stamped with an
>>error of one hour for three weeks or more.
>
>
>Let us not forget about all the embedded devices that automatically
>adjust for DST. I predict that when this change happens elevators
>will plunge passengers to their deaths, airplanes will fall from the
>sky, supertankers will run aground and explode, phone, TV, and banking
>networks will collapse, and people will riot. On the morning of
>Sunday, March 11, 2007 The worlds largest cities will be in flames and
>humanity as we know it will end.
>
>At least that's what the "experts" told us about the Y2K bug. I
>wonder if those are the same experts who are now warning us about
>global warming?
Not to rain on your parade too much, but the reason why Y2K turned out to
be a non-event was because the experts were right, and millions of
man-hours were expended on fixing the problems. If they hadn't, I can
guarantee with personal knowledge that a few million customers of some
rather large financial institutions would have had some extraordinarily
unpleasant surprises in the weeks and months coming up to Y2K. Afterwards,
they would *really* have had some bad days, unless they had large sums of
money hidden in their mattresses.
It always astounds me how many people point to Y2K as an example of
"experts blowing things out of proportion because nothing happened" - when
the reason that nothing significant happened was because a huge legitimate
problem was recognized, identified, and fixed in time. I can't speak to
the effect on other industries, but I can guarantee that people would have
noticed when all of their retirement plan money and other savings magically
disappeared.
- Rich
------------------------------
Message: 9
Date: Mon, 5 Feb 2007 09:10:48 -0500
From: "Danny Messano" <danny_at_messano.net>
Subject: RE: [aprssig] Re: Windows US Daylight Time Change Screwup Looming
It always astounds me how many people point to Y2K as an example of
"experts blowing things out of proportion because nothing happened" - when
the reason that nothing significant happened was because a huge legitimate
problem was recognized, identified, and fixed in time. I can't speak to the
effect on other industries, but I can guarantee that people would have
noticed when all of their retirement plan money and other savings magically
disappeared.
- Rich
I suspect the DST change could be a huge problem if no one was acting on it.
Fact is, apps are being updated, OS's reconfigured, and obsolete hardware is
being replaced as needed, which many will never know about.
Most people don't realize that these are the sort of things that go on daily
behind the walls of many organizations. A new worm makes all the news, and
you'll see some company get a couple hundred infections, but 90,000 other
machines didn't get hit because admins were busy for 3 days rolling out
patches or updating AV/Spyware protection. For many, this means the issue
was just a bunch of hype.. for me, it's a day off after a couple sleepless
nights.
This is why so many people fail to run AV on their machines, run updates,
etc. If it's all blown out of proportion, and just a bunch of hype, why
should I install that crap on my PC if it only slows it down?
My prediction for the distant future is that DST won't mean a thing one day.
We'll all be on UTC, and whole concept of "5PM there" vs "5PM here" will be
gone. I could care less if I go to work at 1300Z and get off at 2300Z, as
long as I am home at 0200Z for the 13th season of "24".
Danny Messano
------------------------------
Message: 10
Date: Mon, 5 Feb 2007 09:39:40 -0500
From: "Robert Bruninga" <bruninga_at_usna.edu>
Subject: RE: [aprssig] Good 30m Reference?
Concerning HF APRS:
>... As a test you can use 'ECHO' to see if you're making
>it out. Most 30m stations digipeat any path with 'ECHO'
>in it. Just don't use it normally else you'll create much QRM.
Not only that, but you wont decode it either, since all the other stations
digipeat it at the same time and so you end up with just a bunch of noise
that does no one any good. Yes, by EAR, you can confirm that something
heard the signal, but it is completely useless for communications.
Yet it is amazing how many HF web pages receommend it! GRRRR...
Bob, WB4APR
------------------------------
Message: 11
Date: Mon, 5 Feb 2007 09:50:20 -0500
From: "Robert Bruninga" <bruninga_at_usna.edu>
Subject: [aprssig] FW: reading aprs path question
>What is the alphanumeric code that appears
>in the beginning of many APRS packets/paths?
>vvvvvv
>Raw packet: K6JLW>APT310,WIDE2-2,qAR,K6TZ...
That is the APRS version field. All APRS packets are sent to an APxxxx
address. The xxxx field lets authors identify the version number of their
softare or hardware. See the TOCALLS.TXT file in the APRS1.1 addendum:
http://www.ew.usna.edu/~bruninga/aprs/aprs11.html
Bob, WB4APR
------------------------------
Message: 12
Date: Mon, 05 Feb 2007 08:53:22 -0600
From: Gregg Wonderly <gregg_at_wonderly.org>
Subject: Re: [aprssig] Re: Windows US Daylight Time Change Screwup Looming
Rich Mulvey wrote:
>I can't speak to the effect on other industries, but I can guarantee that
>people would have noticed when all of their retirement plan money and
>other savings magically disappeared.
There were numerous issues that were fixed in microcontroller environments
in the petroleum products industry.
Gregg Wonderly
W5GGW
------------------------------
Message: 13
Date: Mon, 5 Feb 2007 07:12:57 -0800 (PST)
From: "Curt, WE7U" <archer_at_eskimo.com>
Subject: Re: [aprssig] FW: reading aprs path question
On Mon, 5 Feb 2007, Robert Bruninga wrote:
>>What is the alphanumeric code that appears
>>in the beginning of many APRS packets/paths?
>>vvvvvv
>>Raw packet: K6JLW>APT310,WIDE2-2,qAR,K6TZ...
>
>That is the APRS version field. All APRS packets are sent to an
>APxxxx address.
Well _most_ anyway! There are always exceptions to any rule, and in this
case Mic-E format packets are that exception.
Mic-E packets commandeered that field for part of the positioning info.
They stuff a compressed version of the latitude there and the 100's
indicator of the longitude in order to save bytes. Makes for some
weird-looking packets if you're watching the raw packet data as someone
drives around.
--
Curt, WE7U. APRS Client Comparisons: http://www.eskimo.com/~archer
"Lotto: A tax on people who are bad at math." -- unknown
"Windows: Microsoft's tax on computer illiterates." -- WE7U
"The world DOES revolve around me: I picked the coordinate system!"
------------------------------
Read previous mail | Read next mail
| |
