From: Rhino on
Roedy Green <see_website(a)mindprod.com.invalid> wrote in
news:0be9q51n6p4mldpj3gn6il8eruh68tk49q(a)4ax.com:

> On Fri, 19 Mar 2010 19:38:27 +0000 (UTC), Rhino
> <no.offline.contact.please(a)example.com> wrote, quoted or indirectly
> quoted someone who said :
>
>>How do I get the Java routines to get the right time WHILE STILL HAVING
>>WINDOWS ITSELF DISPLAY THE CORRECT TIME?
>
> Click the clock time in the bottom right.
> click change date and time settings.
> Click change time zone.
> Make sure you have the correct timezone.
> Click "adjust clock for daylight saving".
>

I clicked on the Windows clock icon and found that the time is already set
to 1:37 PM; the date is already correct. The timezone is already set to GMT
-5:00 Eastern Time, Canada and US. The observe daylight saving time box is
checked. In other words, Windows clock is already exactly right.

> Rerun Setclock.

When I launched SetClock, it said the timezone was "EDT : Eastern Daylight
Time (GMT-04:00)" [NOT GMT-5:00] and claimed that my PC clock was set to
2:37 [NOT 1:37]. I clicked on the GetTime button and the correction
appeared as 59 minutes, 59 seconds. I clicked on the SetClock button and
the SetClock GUI now says the PC Clock is 1:37 and the Accurate Clock is
1:37. The Windows Clock now says 12:37, which is an hour early of the
correct time.

Am I not understanding your instructions or is there something wrong here?

If there IS something wrong, where is the problem? In XP? Or could there be
a bug in your SetClock program?


--
Rhino
From: Lew on
Rhino wrote:
> I clicked on the Windows clock icon and found that the time is already set
> to 1:37 PM; the date is already correct. The timezone is already set to GMT

So are we to conclude, as you have not stated it, that the time you checked
was actually 1:37 p.m. Eastern Daylight, and that you are in the Eastern time
zone?

> -5:00 Eastern Time, Canada and US. The observe daylight saving time box is

That is not correct, if you are in the Eastern Time Zone and DST is in effect.
If you are in the Eastern Time Zone and DST is in effect, you are at GMT-04:00.

> checked. In other words, Windows clock is already exactly right.

Your statements leave room for doubt about that.

>> Rerun Setclock.
>
> When I launched SetClock, it said the timezone was "EDT : Eastern Daylight
> Time (GMT-04:00)" [NOT GMT-5:00] and claimed that my PC clock was set to

That is correct. The Eastern Time Zone is currently in DST and is GMT-04:00.

Why do you not think that is correct?

> 2:37 [NOT 1:37]. I clicked on the GetTime button and the correction
> appeared as 59 minutes, 59 seconds. I clicked on the SetClock button and
> the SetClock GUI now says the PC Clock is 1:37 and the Accurate Clock is
> 1:37. The Windows Clock now says 12:37, which is an hour early of the
> correct time.

Your Windows clock must be set wrong.

> Am I not understanding your instructions or is there something wrong here?
>
> If there IS something wrong, where is the problem? In XP? Or could there be
> a bug in your SetClock program?

The problem is in your environment, not the software you keep trying to blame.

--
Lew
From: Rhino on
Lew <noone(a)lewscanon.com> wrote in news:ho2ljt$e44$2(a)news.albasani.net:

> Rhino said :
>>> How do I get the Java routines to get the right time WHILE STILL HAVING
>>> WINDOWS ITSELF DISPLAY THE CORRECT TIME?
>
> Provide an SSCCE!
>

You're kidding, right? If not, how do I provide an SSCCE of what the clock
on my PC is doing?

I could do some screen shots, assuming I can think of some place to put
them where you can see it but short of that, I don't know how to honour
your request.....

--
Rhino


From: Lew on
Rhino said :
>>>> How do I get the Java routines to get the right time WHILE STILL HAVING
>>>> WINDOWS ITSELF DISPLAY THE CORRECT TIME?

Lew wrote:
>> Provide an SSCCE!

Rhino wrote:
> You're kidding, right? If not, how do I provide an SSCCE of what the clock
> on my PC is doing?

No, I mean of the Java code, duh.

> I could do some screen shots, assuming I can think of some place to put
> them where you can see it but short of that, I don't know how to honour
> your request.....

By honoring the actual request.

--
Lew
From: Rhino on
Lew <noone(a)lewscanon.com> wrote in news:ho33sk$h1p$1(a)news.albasani.net:

> Rhino wrote:
>> I clicked on the Windows clock icon and found that the time is
>> already set to 1:37 PM; the date is already correct. The timezone is
>> already set to GMT
>
> So are we to conclude, as you have not stated it, that the time you
> checked was actually 1:37 p.m. Eastern Daylight, and that you are in
> the Eastern time zone?
>
>> -5:00 Eastern Time, Canada and US. The observe daylight saving time
>> box is
>
> That is not correct, if you are in the Eastern Time Zone and DST is in
> effect.
> If you are in the Eastern Time Zone and DST is in effect, you are at
> GMT-04:00.
>
I am indeed in the Eastern Time Zone and DST went into effect last
weekend. However, Windows XP isn't going to let me set the timezone to
Eastern Time GMT-4:00. Windows gives me a drop down menu showing me
umpteen timezone and Eastern GMT-4:00 isn't one of them. It also provides
a checkbox that says "automatically adjust clock for DST", which I have
checked.

>> checked. In other words, Windows clock is already exactly right.
>
> Your statements leave room for doubt about that.
>
>>> Rerun Setclock.
>>
>> When I launched SetClock, it said the timezone was "EDT : Eastern
>> Daylight Time (GMT-04:00)" [NOT GMT-5:00] and claimed that my PC
>> clock was set to
>
> That is correct. The Eastern Time Zone is currently in DST and is
> GMT-04:00.
>
> Why do you not think that is correct?
>
I'm not saying it isn't correct. I'm saying that it is not consistent
with what Windows is telling me. I'm trying to find out if the behaviour
I'm seeing in SetClock is wrong or if Windows is behaving badly.

>> 2:37 [NOT 1:37]. I clicked on the GetTime button and the correction
>> appeared as 59 minutes, 59 seconds. I clicked on the SetClock button
>> and the SetClock GUI now says the PC Clock is 1:37 and the Accurate
>> Clock is 1:37. The Windows Clock now says 12:37, which is an hour
>> early of the correct time.
>
> Your Windows clock must be set wrong.
>
>> Am I not understanding your instructions or is there something wrong
>> here?
>>
>> If there IS something wrong, where is the problem? In XP? Or could
>> there be a bug in your SetClock program?
>
> The problem is in your environment, not the software you keep trying
> to blame.
>

Actually, I'm NOT trying to blame Roedy's SetClock, I'm trying to
understand the behaviour I am getting. If the problem is in Windows,
that's fine, I'm quite prepared to accept that. For the moment, I'm just
trying to be sure that I'm following Roedy's instructions correctly. The
first point of failure with this kind of thing is usually communications
issues over understanding the instructions, at least in my case.

--
Rhino