Re: Time Error
- From: "Pegasus [MVP]" <news@xxxxxxxxxxxxx>
- Date: Wed, 4 Nov 2009 00:53:16 +0100
"Meanon" <meanon@xxxxxxxxx> wrote in message
news:455b7f1c-e2c6-4531-b98e-3a9a611e5c2a@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
On Nov 3, 2:01 pm, "Pegasus [MVP]" <n...@xxxxxxxxxxxxx> wrote:
"Meanon" <mea...@xxxxxxxxx> wrote in message
news:a63508aa-9106-4088-a6ec-4f9ad212927a@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
On Nov 2, 3:52 pm, "Pegasus [MVP]" <n...@xxxxxxxxxxxxx> wrote:
"Meanon" <mea...@xxxxxxxxx> wrote in message
news:7b800583-f95d-4055-b11a-3500c796b567@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
On Nov 2, 3:07 pm, "Pegasus [MVP]" <n...@xxxxxxxxxxxxx> wrote:
"Meanon" <mea...@xxxxxxxxx> wrote in message
news:07a81b81-62c3-4b39-a0a4-a2d858151ccf@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Since the time change on Sunday my WinXP Pro computer shows the
right
time in the Windows clock (in the system tray), but programs that
use
a function call to get the time from the operating system are 1 hour
ahead. I recall something similar happened the last time the clocks
changed.
Does anyone know of a fix for this?
You need to post more details:
- Which programs?
- What function calls?
- Did you tick the box in the Time Zone display marked "Automatically
adjust
clock for daylight saving changes"?
- When you open a Command Prompt, does the command
echo Time=%time%
show the correct time?
Several of my webcam programs as well as a program the controls an
Outdoor LED Display Sign like the ones you see at malls, etc.
Not sure about the specific function call but the software vendor said
they use "a standard function call to get the current time from the
operating system". I assume this would be a function call made from a
C program to a standard system DLL. According to the vendor this is a
known OS bug.
Yes, the time is automatically adjusted by the OS and the proper time
is displayed in the System Tray clock.
When I open a command prompt and echo Time=%time% it displays the
correct time.
TIA.
==============
I've heard this line a few times before: "It's a known OS bug". This is
often the first line of defense by vendors. When pressed for
substantiation
of "known", they invariably fail to deliver. If this was a known bug
then
it
would be widely known by know - Windows XP has been out for many years!
I
recommend you run two more tests before leaning on your vendor. Both
tests
obtain the OS's system time.
1. Paste this line into c:\PCTime.vbs, then double-click the file:
msgbox Date & ", " & Time
2. Insert this formula into some cell of a blank Excel spreadsheet:
=now()
If both tests give you the correct date/time then your vendor has some
explaining to do.- Hide quoted text -
- Show quoted text -
Both methods give the correct time, however, keep in mind the problem
only exists during the 2 week period that is different for the "new"
daylight savings time vs the previous dates. IOW, two weeks after the
time change the programs will display the correct time again. This
makes me wonder if the Microsoft DST patches or just that, a patch not
a permanent proper fix.
=====================
This is certainly a possibility but an extremely remote one. If all tests
display the correct time except for one particular program then there is a
big finger pointing right at that program. I use Kaseya, a web-based
computer administration/management program, and whenever I extract a
Kaseya
report then it adjusts all event date stamps behind my back because the
server is in a different time zone than my own machine. I suspect that
something similar happens with your program. Perhaps the application
maintains a semaphore file that it reads once every hour. When it finds a
gap, caused by the Daylight Switch, then it persists for a couple weeks,
"thinking" that it missed a reading.
If you could find just one single program that is not related in any way
to
your problem application and that exhibits the same problem then you would
have a good case for a Windows bug. If you can't then your case is very
weak. As I said before: There are a few million WinXP installations that
have been running since around 2001 and I am not aware of a single report
about this type of problem. Has your vendor been able to support his claim
that this is a "known bug"? If it's "known" then he should be able to
deliver the goods with ease!- Hide quoted text -
- Show quoted text -
Well, that is exactly what I have! ;-)
The iSpy webcam program has the same problem as the Adtron 7000
program that drives our LED sign. The two progrmas are from completely
different vendors and gave nothing in common.
However, you're right *most* programs seem to be able to get the right
time. I guess I'll continue to persue this with the Adtron 7000
vendor.
Thanks for you input!
====================
If you can post a step-by-step process that lets me duplicate your
observation with iSpy then I'm happy to test it myself.
.
- Follow-Ups:
- Re: Time Error
- From: Meanon
- Re: Time Error
- References:
- Time Error
- From: Meanon
- Re: Time Error
- From: Pegasus [MVP]
- Re: Time Error
- From: Meanon
- Re: Time Error
- From: Pegasus [MVP]
- Re: Time Error
- From: Meanon
- Re: Time Error
- From: Pegasus [MVP]
- Re: Time Error
- From: Meanon
- Time Error
- Prev by Date: RE: Missing audio driver
- Next by Date: Re: blue screen of death!
- Previous by thread: Re: Time Error
- Next by thread: Re: Time Error
- Index(es):
Relevant Pages
|
