Welcome to Omgili,
Omgili ( Oh My God I Love It ;) is a search engine for discussions. With Omgili you can find answers and solutions, debates, discussions, personal experiences, opinions and more... To learn more about Omgili click here.
This is a complete preview of the discussion as it was indexed by Omgili crawlers. Use this preview if the original discussion is unavailable.
Click here to view the original discussion.
 |
|
 |
|
PDA DST update does not take effect - PPczone.net forums
My Jornada 720 did not update, but its amazing that the VxUtil time app
connecting to the server time.nist.gov does not update.
I clicked on the
set CE time with that server, and it did not update the CE to the latest
time.
Its a shame that I will have to manually set this.
Also my Palm Zire 72 (which I downloaded the new DST update and hot
synced it) did not update.
Something funny is going on.
Did anyone else have the same problem?
John
--
Romans 6:23 For the wages of sin is death,
but the gift of God is eternal life
in Christ Jesus our Lord.
CERM-Church Education Resource Ministries
http://www.cerm.info
|
|
 |
|
 |
|
|
|
|
You know, I don't think that hitting NIST, or any other NTP server would
neccesarily set your time right.
It has no idea where you are.
So the best
it can do is set either the minutes/seconds, or set GMT and let you display
hours based on the TimeZone you set.
Bet your minutes and seconds are dead
on though.
"Bible John" <johnw_94020@yahoo.com>
Johnw_94020-1B3661.08563511032007@msnews.microsoft.com...
>
My Jornada 720 did not update, but its amazing that the VxUtil time app
>
Connecting to the server time.nist.gov does not update.
I clicked on the
>
Set CE time with that server, and it did not update the CE to the latest
>
Time. Its a shame that I will have to manually set this.
>
>
Also my Palm Zire 72 (which I downloaded the new DST update and hot
>
Synced it) did not update.
>
>
Something funny is going on.
Did anyone else have the same problem?
>
>
>
>
John
> --
>
Romans 6:23 For the wages of sin is death,
>
But the gift of God is eternal life
>
In Christ Jesus our Lord.
>
CERM-Church Education Resource Ministries
>
Http://www.cerm.info
|
|
|
|
|
|
|
|
|
On Mar 11, 9:56 am, Bible John Quote: :
>
My Jornada 720 did not update
My Toshiba E805 Running 2003 SE did not update it's clock.
On the PC
side I'm running Vista and Outlook 2007.
All looks fine on the PC side.
I manually adjusted the clock on the PDA and it seems ok.
The
appointments have the correct time.
I thought the PDA auto sync'd to the PC clock?
|
|
|
|
|
|
|
|
|
I am also having trouble with my handheld device.
I have a dell AXIM with
Windows Mobile using Activesync.
I have updated my Windows XP professional and Outlook 2003 and they are
fine.
I did the fix for my mobile device and my time is not changing and all
my appointments are off by 1 hour.
Anybody have any ideas.
I have installed removed and installed twice.
Becky
Quote: :
>
On Mar 11, 9:56 am, Bible John Quote: :
>
> My Jornada 720 did not update
>
>
My Toshiba E805 Running 2003 SE did not update it's clock.
On the PC
> side I'm running Vista and Outlook 2007.
>
>
All looks fine on the PC side.
>
>
I manually adjusted the clock on the PDA and it seems ok.
The
> appointments have the correct time.
>
>
I thought the PDA auto sync'd to the PC clock?
>
>
|
|
|
|
|
|
|
|
|
Bible John Quote: :
>
My Jornada 720 did not update, but its amazing that the VxUtil time app
>
Connecting to the server time.nist.gov does not update.
I clicked on the
>
Set CE time with that server, and it did not update the CE to the latest
>
Time. Its a shame that I will have to manually set this.
That's the nature of time servers.
They set your clock to the exact
Greenwich Mean Time, as that's the one time that's fixed.
All other
times are derived from that by applying time zone information and
whatever local Daylight Saving Time rules exist.
It takes an update tot
he DST rules on your device to make that work automatically.
PCs
running Windows XP or Vista with the appropriate patches and Macs
running OS X 10.3.9 through 10.4.4 with the appropriate patch, or with
10.4.5 or later, will change their clocks appropriately.
--
<http://designsbymike.biz/macconsultshop.shtml>
Mac-themed T-shirts
<http://designsbymike.biz/musings.shtml>
Mostly muckraking T-shirts
<http://designsbymike.biz/prius.shtml>
Prius shirts & bumper stickers
<http://cafepress.com/comedancing>
Ballroom dance-themed shirts & gift
|
|
|
|
|
|
|
|
|
In article <1hutnhb.6pk2nupxe95lN%mikePOST@TOGROUPmacconsult.
Com>,
mikePOST@TOGROUPmacconsult.com (Mike Quote: :
>
Bible John Quote: :
>
>
> My Jornada 720 did not update, but its amazing that the VxUtil time app
>
> connecting to the server time.nist.gov does not update.
I clicked on the
>
> set CE time with that server, and it did not update the CE to the latest
>
> time. Its a shame that I will have to manually set this.
>
>
That's the nature of time servers.
They set your clock to the exact
>
Greenwich Mean Time, as that's the one time that's fixed.
All other
> times are derived from that by applying time zone information and
>
Whatever local Daylight Saving Time rules exist.
It takes an update tot
>
He DST rules on your device to make that work automatically.
PCs
> running Windows XP or Vista with the appropriate patches and Macs
>
Running OS X 10.3.9 through 10.4.4 with the appropriate patch, or with
>
10.4.5 or later, will change their clocks appropriately.
I thought Mac OS 9 also connected to the Time Servers?
I'll just manually change my CE clock.
I'll also have to do it to my
GPS.
Or maybe I'll just wait a few weeks.
John
--
Romans 6:23 For the wages of sin is death,
but the gift of God is eternal life
in Christ Jesus our Lord.
CERM-Church Education Resource Ministries
http://www.cerm.info
|
|
|
|
|
|
|
|
|
Bible John Quote: :
>
I thought Mac OS 9 also connected to the Time Servers?
Yes, it did.
I mentioned OS versions for which automatic DST updates
are available, and it's not among them.
--
<http://designsbymike.biz/macconsultshop.shtml>
Mac-themed T-shirts
<http://designsbymike.biz/musings.shtml>
Mostly muckraking T-shirts
<http://designsbymike.biz/prius.shtml>
Prius shirts & bumper stickers
<http://cafepress.com/comedancing>
Ballroom dance-themed shirts & gift
|
|
|
|
|
|
|
|
|
"Bible John" <johnw_94020@yahoo.com>
Johnw_94020-1B3661.08563511032007@msnews.microsoft.com...
>
My Jornada 720 did not update, but its amazing that the VxUtil time app
>
Connecting to the server time.nist.gov does not update.
I clicked on the
>
Set CE time with that server, and it did not update the CE to the latest
>
Time. Its a shame that I will have to manually set this.
>
>
Also my Palm Zire 72 (which I downloaded the new DST update and hot
>
Synced it) did not update.
>
>
Something funny is going on.
Did anyone else have the same problem?
>
>
Well, I'll just say that the time is messed up on all of my computers to
some degree.
Either the time itself, or like others, things in Outlook with
the computers running Win.
All my WWVB clocks in the house?
(Those so-called "atomic" consumer clocks
that synch a couple time per day with NIST out in Colorado over HF radio).
Every one of them seamlessly and transparantly updated correctly.
NIST does it right by having DST controlled by the "server" instead of it
being processed by the end device.
Frame format for NIST WWVB:
http://tf.nist.gov/timefreq/stations/wwvbtimecode.htm
Congress could change DST to be any day of the year and it wouldn't matter
to the "clients".
NTP (how consumer computers do time synching) is seriously flawed in this
regard.
It needs to be like the WWVB frame.
|
|
|
|
|
|
|
|
|
Got everything patched for the new DST now...
I still maintain that WWVB does it the "right way" by having the DST flag on
their side...
http://tf.nist.gov/timefreq/stations/wwvbtimecode.htm
- All my WWVB clocks, including a freaking wrist watch, updated correctly
with zero intervention.
(Why should a clock, on the client side, need a "patch"?
That is rediculous.
DST should be controlled from the serving side.)
- Windows computers took about a minute each to patch.
(Download and install the MS patch.)
- Linux computers, true to the "Linux form", took a freaking half hour to
patch.
Mostly from just wadding through the technobabble.
(Once I got one patched, the other one only a took a minute to patch
though.)
- Jornada 720: I ain't worried about it.
Just going to disable DST.
Its
not like its difficult to manually offset the hour twice a year...
Now to change the time on the stupid microwave...
:-)
....and DVD players, TV's, dumb clocks, alarm clocks, etc..
Nah, forget the alarm clock.
That is an excuse to be late to work
tomorrow...
:-)
|
|
|
|
|
|
|
|
|
OK, so how does the transmitter know where you are?
The flag just indicates
whether we are or are not in DST.
There still needs to be logic in the
client about whether to do someting with that info or not.
The problem is
not with the actual time, it is with all the appointments that are based on
it.
"ercsa" <none@none.nospam.non>
45f4d2b0$0$28084$4c368faf@roadrunner.com...
>
Got everything patched for the new DST now...
>
>
I still maintain that WWVB does it the "right way" by having the DST flag
>
On their side...
>
>
Http://tf.nist.gov/timefreq/stations/wwvbtimecode.htm
>
>
- All my WWVB clocks, including a freaking wrist watch, updated correctly
>
With zero intervention.
>
(Why should a clock, on the client side, need a "patch"?
That is
> rediculous.
DST should be controlled from the serving side.)
>
>
- Windows computers took about a minute each to patch.
>
(Download and install the MS patch.)
>
>
- Linux computers, true to the "Linux form", took a freaking half hour to
>
Patch. Mostly from just wadding through the technobabble.
>
(Once I got one patched, the other one only a took a minute to patch
>
Though.)
>
>
- Jornada 720: I ain't worried about it.
Just going to disable DST.
Its
> not like its difficult to manually offset the hour twice a year...
>
>
Now to change the time on the stupid microwave...
:-)
>
> ...and DVD players, TV's, dumb clocks, alarm clocks, etc..
>
>
Nah, forget the alarm clock.
That is an excuse to be late to work
>
Tomorrow... :-)
>
>
>
>
>
>
|
|
|
|
|
|
|
|
|
On Mar 11, 11:59 pm, "Sven" Quote: :
>
OK, so how does the transmitter know where you are?
The flag just indicates
>
Whether we are or are not in DST.
There still needs to be logic in the
>
Client about whether to do someting with that info or not.
The problem is
>
Not with the actual time, it is with all the appointments that are based on
>
It.
>
Transmitter doesn't know.
You tell the device what time zone you're
in (probably how the PC clock works too).
Some of the "Atomic" clocks
don't have a specific DST switch so you have to manually offset your
timezone if you live in a place that doesn't observe.
|
|
|
|
|
|
|
|
|
"Sven" <sejohannsen@hotmail.com>
%23Xs%23uPHZHHA.2448@TK2MSFTNGP02.phx.gbl...
>
OK, so how does the transmitter know where you are?
The flag just
>
Indicates whether we are or are not in DST.
There still needs to be logic
>
In the client about whether to do someting with that info or not.
The
> problem is not with the actual time, it is with all the appointments that
>
Are based on it.
Nod, but the logic that it has to take care of locally is kept to a bare
mininum.
You simply tell WWVB devices what time zone you are in and whether it not to
make use of the DST flag.
Thats it.
Set once and forget.
DST is simple.
If you live somewhere where DST is used, half the year you
are in standard time and the other half you are in daylight saving time.
There is no reason why the start/stop dates need to be hardcoded locally.
It should just be controlled by a simple flag from whatever you are synching
with.
The simple fact is that WWVB devices "just worked", while computers doing
NTP required "patches".
Keep it short and simple...
|
|
|
|
|
|
|
|
|
At 12 Mar 2007 10:35:33 -0400 Quote: :
>
You simply tell WWVB devices what time zone you are in and whether it
not to
>
Make use of the DST flag.
>
>
Thats it. Set once and forget.
Which is fine IF everyone uses the same dates for the beginning and
ending of DST, like the North America does.
The WWVB solution might not
work for areas where different countries have different start/end dates.
>
DST is simple. If you live somewhere where DST is used, half the year
you
>
Are in standard time and the other half you are in daylight saving
time.
>
There is no reason why the start/stop dates need to be hardcoded locally.
>
It should just be controlled by a simple flag from whatever you are
synching
>
With.
Again, assuming everyone has the same DST pe iod, or perhaps one needs
multiple "flags!"
>
The simple fact is that WWVB devices "just worked", while computers
doing
>
NTP required "patches".
>
>
Keep it short and simple...
Even simpler- a button/switch/setting on the device for "it's currently
DST"- now no internal coding or flag is needed!
;-)
|
|
|
|
|
|
|
|
|
Quote: :
> Got everything patched for the new DST now...
>
>
- Jornada 720: I ain't worried about it.
Just going to disable DST.
Its
> not like its difficult to manually offset the hour twice a year...
>
Having to manually offset the hour isn't the problem;
When you do that
all your appointments will move and be off by an hour from the time you
specified.
|
|
|
|
|
|
|
|
|
"Todd Allcock" <elecconnec@AmericaOnLine.com>
Et3ttt$1ev$4@aioe.org...
>
At 12 Mar 2007 10:35:33 -0400 Quote: :
>
>
>>
You simply tell WWVB devices what time zone you are in and whether it
>
Not to
>> make use of the DST flag.
>>
>>
Thats it. Set once and forget.
>
>
Which is fine IF everyone uses the same dates for the beginning and
>
Ending of DST, like the North America does.
I posted this previously:
---
|
|
|
|
|
|
|
|