Time zone puzzle

Is it possible that applications can somehow fail to use the PC's time
zone correctly? Or for that to be over-ruled by a BIOS facility?

My time zone is (UTC+OO:00) Dublin, Edinburgh, Lisbon, London. And I
have never changed it. But I'm baffled by an obscure problem with my
mapping program, Memory-Map, which I'd regarded as a bug. In short, when
I open any GPX file of a GPS recording made in the summer, two problems
arise:

1. It displays the time one hour earlier than the correct time. IOW it
displays the first trackpoint of a July walk that started at 09:00 as
08:00.

2. When I save the GPX it subtracts another hour from all the time
stamps.

My version of Mem-Map is about 5 years old and Mem-Map support are
unable to reproduce the problem on a current version.

The obvious conclusion would be that it is indeed a bug in this old
version, but two things are prompting me to challenge that:

- I don't recall recognising this problem the last time I did similar
intensive work with GPX files, maybe a year ago (and many times before
that).

- Googling has got me suspecting Win 10 and/or my BIOS. Mostly stuff
that's technically over my head. Mem-Map's behaviour is naturally
critically dependent on the PC's time zone. Although Date/Time has been
constantly displayed correctly in the tray, could some lower level
function have interfered/corrupted in some way?

Win 10 here is currently at Version 1709 (OS Build 16299.309)

Any insights would be much appreciated please.

Terry, East Grinstead, UK

Terry Pinnell wrote:

Is it possible that applications can somehow fail to use the PC's time
zone correctly?

Programmers can make a million mistakes with handling of time, rather
than using standard libraries to help them, it sounds like in the case
of memory-map that they may have assumed the time zone from the time the
file was created will be the same as the time zone now.

On Fri, 16 Mar 2018 18:04:04 +0000, Terry Pinnell wrote:

Is it possible that applications can somehow fail to use the PC's time
zone correctly? Or for that to be over-ruled by a BIOS facility?

My time zone is (UTC+OO:00) Dublin, Edinburgh, Lisbon, London. And I
have never changed it. But I'm baffled by an obscure problem with my
mapping program, Memory-Map, which I'd regarded as a bug. In short, when
I open any GPX file of a GPS recording made in the summer, two problems
arise:

1. It displays the time one hour earlier than the correct time. IOW it
displays the first trackpoint of a July walk that started at 09:00 as
08:00.


Seems it assumes DST was in effect at that time.

On 16/03/2018 21:39, ray carter wrote:
On Fri, 16 Mar 2018 18:04:04 +0000, Terry Pinnell wrote:

Is it possible that applications can somehow fail to use the PC's time
zone correctly? Or for that to be over-ruled by a BIOS facility?

My time zone is (UTC+OO:00) Dublin, Edinburgh, Lisbon, London. And I
have never changed it. But I'm baffled by an obscure problem with my
mapping program, Memory-Map, which I'd regarded as a bug. In short, when
I open any GPX file of a GPS recording made in the summer, two problems
arise:

1. It displays the time one hour earlier than the correct time. IOW it
displays the first trackpoint of a July walk that started at 09:00 as
08:00.

Seems it assumes DST was in effect at that time.

IOW the OP should wait until 25th March when UK starts its Summer Time!!

We get all sorts here worried about almost everything. The OP should
spend some time (if he/she is bored with life) scanning not only his
brain but his machine as well using Microsoft's State of the Art
Anti-Virus App. Link below.



/--- This email has been checked for viruses by
Windows Defender software.
//https://www.microsoft.com/en-gb/windows/comprehensive-security/


--
With over 600 million devices now running Windows 10, customer
satisfaction is higher than any previous version of windows.

On Fri, 16 Mar 2018 21:49:10 +0000, Good Guy wrote:

On 16/03/2018 21:39, ray carter wrote:
On Fri, 16 Mar 2018 18:04:04 +0000, Terry Pinnell wrote:

Is it possible that applications can somehow fail to use the PC's time
zone correctly? Or for that to be over-ruled by a BIOS facility?

My time zone is (UTC+OO:00) Dublin, Edinburgh, Lisbon, London. And I
have never changed it. But I'm baffled by an obscure problem with my
mapping program, Memory-Map, which I'd regarded as a bug. In short,
when I open any GPX file of a GPS recording made in the summer, two
problems arise:

1. It displays the time one hour earlier than the correct time. IOW it
displays the first trackpoint of a July walk that started at 09:00 as
08:00.

Seems it assumes DST was in effect at that time.

IOW the OP should wait until 25th March when UK starts its Summer Time!!

We get all sorts here worried about almost everything. The OP should
spend some time (if he/she is bored with life) scanning not only his
brain but his machine as well using Microsoft's State of the Art
Anti-Virus App. Link below.

You were told to go away, why are you still posting.

ray carter wrote:

On Fri, 16 Mar 2018 18:04:04 +0000, Terry Pinnell wrote:

Is it possible that applications can somehow fail to use the PC's time
zone correctly? Or for that to be over-ruled by a BIOS facility?

My time zone is (UTC+OO:00) Dublin, Edinburgh, Lisbon, London. And I
have never changed it. But I'm baffled by an obscure problem with my
mapping program, Memory-Map, which I'd regarded as a bug. In short, when
I open any GPX file of a GPS recording made in the summer, two problems
arise:

1. It displays the time one hour earlier than the correct time. IOW it
displays the first trackpoint of a July walk that started at 09:00 as
08:00.


Seems it assumes DST was in effect at that time.

Agreed, but can I rule out any other cause apart from a bug in
Memory-Map itself?

Terry, East Grinstead, UK

On Fri, 16 Mar 2018 18:04:04 +0000, Terry Pinnell
wrote:

Is it possible that applications can somehow fail to use the PC's time
zone correctly? Or for that to be over-ruled by a BIOS facility?

My time zone is (UTC+OO:00) Dublin, Edinburgh, Lisbon, London. And I
have never changed it. But I'm baffled by an obscure problem with my
mapping program, Memory-Map, which I'd regarded as a bug. In short, when
I open any GPX file of a GPS recording made in the summer, two problems
arise:

1. It displays the time one hour earlier than the correct time. IOW it
displays the first trackpoint of a July walk that started at 09:00 as
08:00.

2. When I save the GPX it subtracts another hour from all the time
stamps.

My version of Mem-Map is about 5 years old and Mem-Map support are
unable to reproduce the problem on a current version.

The obvious conclusion would be that it is indeed a bug in this old
version, but two things are prompting me to challenge that:

- I don't recall recognising this problem the last time I did similar
intensive work with GPX files, maybe a year ago (and many times before
that).

- Googling has got me suspecting Win 10 and/or my BIOS. Mostly stuff
that's technically over my head. Mem-Map's behaviour is naturally
critically dependent on the PC's time zone. Although Date/Time has been
constantly displayed correctly in the tray, could some lower level
function have interfered/corrupted in some way?

Win 10 here is currently at Version 1709 (OS Build 16299.309)

Any insights would be much appreciated please.

Terry, East Grinstead, UK


I suppose we have to live with time zones, but the Summer
time/Daylight saving contrivance is the work of Satan.

We will never know (ie it is suppressed) how many people die because
facility impairment due to di-annual jet-lagging.

And how many (also suppressed) injuries caused by the unfortunate who
fall off ladders adjusting clocks twice a year.

And how many (suppressed too) road crashes caused by having to drive
into the rising/setting sun not once but twice a year.

And how many expensive mistakes caused by not accounting for the
contrivance.

And then there are our bowels that have to make some sort of internal
adjustment...!!

Too few nations refuse to get involved with the clock-adjustment
nonsense. Yet there are some.