but if Windows is only using A64 it doesn't matter.
Microsoft supply compilers that can target 32-bit code, and run-time libraries for 32-bit programs. I've never tried building anything
on ARM Windows for 32-bit so I don't know how well they work. I
don't know if ARM Windows 11, which is always a 64-bit OS, will
notice that the hardware is incapable of running A32/T32 ...
In article <memo.20251007223453.10624Y@jgd.cix.co.uk>, jgd@cix.co.uk
(John Dallman) wrote:
but if Windows is only using A64 it doesn't matter.
Microsoft supply compilers that can target 32-bit code, and run-time
libraries for 32-bit programs. I've never tried building anything
on ARM Windows for 32-bit so I don't know how well they work. I
don't know if ARM Windows 11, which is always a 64-bit OS, will
notice that the hardware is incapable of running A32/T32 ...
ARM Windows 11 is not interested in running 32-bit executables and
refuses on looking at them. I don't have any ARM Windows 10 left to try
them on.
On 2026-10-04, John Dallman <jgd@cix.co.uk> wrote:
In article <memo.20251007223453.10624Y@jgd.cix.co.uk>, jgd@cix.co.uk
(John Dallman) wrote:
but if Windows is only using A64 it doesn't matter.
Microsoft supply compilers that can target 32-bit code, and run-time
libraries for 32-bit programs. I've never tried building anything
on ARM Windows for 32-bit so I don't know how well they work. I
don't know if ARM Windows 11, which is always a 64-bit OS, will
notice that the hardware is incapable of running A32/T32 ...
ARM Windows 11 is not interested in running 32-bit executables and
refuses on looking at them. I don't have any ARM Windows 10 left to try
them on.
I am in two minds about this.
On the one hand, I strongly believe in backwards compatibility.
On the other hand, we are only a little over 11 years to the physical
reality that is 2038.
BTW, I also worry that because we did such a good job with Y2K, because
we got the resources and people we needed in plenty of time due to the >publicity, that people may not take 2038 seriously enough until it is too >late and the disaster is upon us.
On 10/5/2026 10:16 AM, Dan Cross wrote:
In article <11a04vp$tous$1@dont-email.me>,Windows NT is more VMS than Unix. Internally it use 64 bit
Simon Clubley <clubley@remove_me.eisner.decus.org-Earth.UFP> wrote:
On the other hand, we are only a little over 11 years to the physical
reality that is 2038.
Is time on 32-bit Windows measured as a signed 32-bit integer
tracking seconds since Jan 1, 1970, UTC? Wikipedia suggests
something like that.
If correct, then yes, it is a problem. If not, then I don't see
any reason why one could not use a 32-bit executable with 64-bit
`time_t`.
with 100 ns units since 1601 (not 1858).
C time_t switched to 64 bit as default on both 32 bit and 64 bit
Windows two decades ago.
Of course someone can have very old binaries or newer
binaries that for whatever reason has been built with
_USE_32BIT_TIME_T.
In article <11a04vp$tous$1@dont-email.me>,Windows NT is more VMS than Unix. Internally it use 64 bit
Simon Clubley <clubley@remove_me.eisner.decus.org-Earth.UFP> wrote:
On the other hand, we are only a little over 11 years to the physical
reality that is 2038.
Is time on 32-bit Windows measured as a signed 32-bit integer
tracking seconds since Jan 1, 1970, UTC? Wikipedia suggests
something like that.
If correct, then yes, it is a problem. If not, then I don't see
any reason why one could not use a 32-bit executable with 64-bit
`time_t`.
On 10/5/2026 10:16 AM, Dan Cross wrote:And in case someone is interested in VMS then it is:
In article <11a04vp$tous$1@dont-email.me>,Windows NT is more VMS than Unix. Internally it use 64 bit
Simon Clubley-a <clubley@remove_me.eisner.decus.org-Earth.UFP> wrote:
On the other hand, we are only a little over 11 years to the physical
reality that is 2038.
Is time on 32-bit Windows measured as a signed 32-bit integer
tracking seconds since Jan 1, 1970, UTC?-a Wikipedia suggests
something like that.
If correct, then yes, it is a problem.-a If not, then I don't see
any reason why one could not use a 32-bit executable with 64-bit
`time_t`.
with 100 ns units since 1601 (not 1858).
C time_t switched to 64 bit as default on both 32 bit and 64 bit
Windows two decades ago.
Of course someone can have very old binaries or newer
binaries that for whatever reason has been built with
_USE_32BIT_TIME_T.
Is time on 32-bit Windows measured as a signed 32-bit integer
tracking seconds since Jan 1, 1970, UTC? Wikipedia suggests
something like that.
Dan Cross <cross@spitfire.i.gajendra.net> wrote:SYSTEMTIME is more like struct tm than like time_t.
Is time on 32-bit Windows measured as a signed 32-bit integer
tracking seconds since Jan 1, 1970, UTC? Wikipedia suggests
something like that.
No, Windows time is not epoch time. And Windows uses several different
time formats for different things. SYSTEMTIME is stored as a weird and sloppy structure, but the times in the filesystem are stored in a totally different format.
In article <11a0d4k$11ecp$1@dont-email.me>,
Arne Vajh|+j <arne@vajhoej.dk> wrote:
On 10/5/2026 10:16 AM, Dan Cross wrote:
In article <11a04vp$tous$1@dont-email.me>,Windows NT is more VMS than Unix. Internally it use 64 bit
Simon Clubley <clubley@remove_me.eisner.decus.org-Earth.UFP>
wrote:
On the other hand, we are only a little over 11 years to the
physical reality that is 2038.
Is time on 32-bit Windows measured as a signed 32-bit integer
tracking seconds since Jan 1, 1970, UTC? Wikipedia suggests
something like that.
If correct, then yes, it is a problem. If not, then I don't see
any reason why one could not use a 32-bit executable with 64-bit
`time_t`.
with 100 ns units since 1601 (not 1858).
C time_t switched to 64 bit as default on both 32 bit and 64 bit
Windows two decades ago.
Of course someone can have very old binaries or newer
binaries that for whatever reason has been built with
_USE_32BIT_TIME_T.
From
https://en.wikipedia.org/wiki/Year_2038_problem#Vulnerable_systems,
|As of circa Windows 10 version 22H2, if an x86 (32-bit) device
|has not been turned on at the rollover point, but is started up
|after the rollover, the system clock can skip ahead to 12 April
|2160, and the date options in Windows 10's main settings menu
|does not show any selectable numbers.[13]
This suggests they're doing the same, "treat a 32-bit int as
unsigned" trick that Kick McKusick and the FreeBSD people did
for UFS2, but have a bug somewhere.
- Dan C.
On 10/5/2026 10:44 AM, Arne Vajhoj wrote:
And in case someone is interested in VMS then it is:
100 ns units since 1858 internally and 32 bit unsigned
time_t.
So VMS has a 2106 problem not a 2038 problem.
Arne
Is time on 32-bit Windows measured as a signed 32-bit integer
tracking seconds since Jan 1, 1970, UTC? Wikipedia suggests
something like that.
If correct, then yes, it is a problem. If not, then I don't see
any reason why one could not use a 32-bit executable with 64-bit
`time_t`.
In article <11a0bfu$lkg$1@reader2.panix.com>,
cross@spitfire.i.gajendra.net (Dan Cross) wrote:
Is time on 32-bit Windows measured as a signed 32-bit integer
tracking seconds since Jan 1, 1970, UTC? Wikipedia suggests
something like that.
If correct, then yes, it is a problem. If not, then I don't see
any reason why one could not use a 32-bit executable with 64-bit
`time_t`.
As of Visual Studio 2022, and several previous versions, time_t is 64-bit
on 32- and 64-bit Windows. The implementation in the run-time libraries
may be defective, of course.
On Mon, 5 Oct 2026 10:52:28 -0400
Arne Vajhoj <arne@vajhoej.dk> wrote:
On 10/5/2026 10:44 AM, Arne Vajhoj wrote:
And in case someone is interested in VMS then it is:
100 ns units since 1858 internally and 32 bit unsigned
time_t.
So VMS has a 2106 problem not a 2038 problem.
I can not figure out what you have in mind.
In article <20261005224717.00004719@yahoo.com>,
Michael S <already5chosen@yahoo.com> wrote:
On Mon, 5 Oct 2026 10:52:28 -0400
Arne Vajhoj <arne@vajhoej.dk> wrote:
On 10/5/2026 10:44 AM, Arne Vajhoj wrote:
And in case someone is interested in VMS then it is:
100 ns units since 1858 internally and 32 bit unsigned
time_t.
So VMS has a 2106 problem not a 2038 problem.
I can not figure out what you have in mind.
He's referring to when VMS's `time_t` rolls over. Since it is
an unsigned 32-bit int, overflow will be in 2106, not 2038, as
in the case for signed 32-bit `time_t` on other systems.
It is true that this is not something that the _operating
system_ itself cares about, as it's in the C RTL (or anything
that uses the Unix epoch), but it's a problem for VMS in the
sense that it still needs to be fixed, tested, and shipped in
less than 100 years.
- Dan C.
On Wed, 7 Oct 2026 11:58:27 -0000 (UTC)
cross@spitfire.i.gajendra.net (Dan Cross) wrote:
In article <20261005224717.00004719@yahoo.com>,
Michael S <already5chosen@yahoo.com> wrote:
On Mon, 5 Oct 2026 10:52:28 -0400=20
Arne Vajh=F8j <arne@vajhoej.dk> wrote:
=20
On 10/5/2026 10:44 AM, Arne Vajh=F8j wrote:
And in case someone is interested in VMS then it is:
=20
100 ns units since 1858 internally and 32 bit unsigned
time_t.
=20
So VMS has a 2106 problem not a 2038 problem. =20
I can not figure out what you have in mind. =20
He's referring to when VMS's `time_t` rolls over. Since it is
an unsigned 32-bit int, overflow will be in 2106, not 2038, as
in the case for signed 32-bit `time_t` on other systems.
=20
What I didn't get is how the problem related to 1858.
Now I understand that it is not related.
Michael S <already5chosen@yahoo.com> writes:
On Wed, 7 Oct 2026 11:58:27 -0000 (UTC)
cross@spitfire.i.gajendra.net (Dan Cross) wrote:
In article <20261005224717.00004719@yahoo.com>,
Michael S <already5chosen@yahoo.com> wrote:
On Mon, 5 Oct 2026 10:52:28 -0400=20
Arne Vajh=F8j <arne@vajhoej.dk> wrote:
=20
On 10/5/2026 10:44 AM, Arne Vajh=F8j wrote:
And in case someone is interested in VMS then it is:
=20
100 ns units since 1858 internally and 32 bit unsigned
time_t.
=20
So VMS has a 2106 problem not a 2038 problem. =20
I can not figure out what you have in mind. =20
He's referring to when VMS's `time_t` rolls over. Since it is
an unsigned 32-bit int, overflow will be in 2106, not 2038, as
in the case for signed 32-bit `time_t` on other systems.
=20
What I didn't get is how the problem related to 1858.
Now I understand that it is not related.
Peripherally related, perhaps. The baseline for VMS
time is 17 November 1858 00:00:00.
On 07/10/2026 21:54, Scott Lurndal wrote:
Michael S <already5chosen@yahoo.com> writes:
On Wed, 7 Oct 2026 11:58:27 -0000 (UTC)
cross@spitfire.i.gajendra.net (Dan Cross) wrote:
In article <20261005224717.00004719@yahoo.com>,
Michael S <already5chosen@yahoo.com> wrote:
On Mon, 5 Oct 2026 10:52:28 -0400=20
Arne Vajh=F8j <arne@vajhoej.dk> wrote:
=20
On 10/5/2026 10:44 AM, Arne Vajh=F8j wrote:
And in case someone is interested in VMS then it is:
=20
100 ns units since 1858 internally and 32 bit unsigned
time_t.
=20
So VMS has a 2106 problem not a 2038 problem. =20
I can not figure out what you have in mind. =20
He's referring to when VMS's `time_t` rolls over. Since it is
an unsigned 32-bit int, overflow will be in 2106, not 2038, as
in the case for signed 32-bit `time_t` on other systems.
=20
What I didn't get is how the problem related to 1858.
Now I understand that it is not related.
Peripherally related, perhaps. The baseline for VMS
time is 17 November 1858 00:00:00.
For Vax basic users, it was 1970, so we had to fix it before 2003 - we
did it with Y2K
Chris Townley <news@cct-net.co.uk> writes:
On 07/10/2026 21:54, Scott Lurndal wrote:
Michael S <already5chosen@yahoo.com> writes:
On Wed, 7 Oct 2026 11:58:27 -0000 (UTC)
cross@spitfire.i.gajendra.net (Dan Cross) wrote:
In article <20261005224717.00004719@yahoo.com>,
Michael S <already5chosen@yahoo.com> wrote:
On Mon, 5 Oct 2026 10:52:28 -0400=20
Arne Vajh=F8j <arne@vajhoej.dk> wrote:
=20
On 10/5/2026 10:44 AM, Arne Vajh=F8j wrote:
And in case someone is interested in VMS then it is:
=20
100 ns units since 1858 internally and 32 bit unsigned
time_t.
=20
So VMS has a 2106 problem not a 2038 problem. =20
I can not figure out what you have in mind. =20
He's referring to when VMS's `time_t` rolls over. Since it is
an unsigned 32-bit int, overflow will be in 2106, not 2038, as
in the case for signed 32-bit `time_t` on other systems.
=20
What I didn't get is how the problem related to 1858.
Now I understand that it is not related.
Peripherally related, perhaps. The baseline for VMS
time is 17 November 1858 00:00:00.
For Vax basic users, it was 1970, so we had to fix it before 2003 - we
did it with Y2K
That seems strange, unless you were running your BASIC
interpreter on UnixV32 or BSD (the unix epoch started
Dec 31, 1969 at midnight).
TIME function in VSI BASIC seems to have been 'number of seconds since midnight' as
a floating point value. I mainly used Macro32, Bliss32 and VAX Pascal, where I had access
to the VMS starlet functions for time management and inquiry.
VSI BASIC Returns
0 The amount of time elapsed since midnight in seconds
1 The CPU time of the current process in tenths of a second
2 The connect time of the current process in minutes
TIME$ returns a string with the current time.
On 07/10/2026 23:14, Scott Lurndal wrote:
Chris Townley <news@cct-net.co.uk> writes:
On 07/10/2026 21:54, Scott Lurndal wrote:
Michael S <already5chosen@yahoo.com> writes:
On Wed, 7 Oct 2026 11:58:27 -0000 (UTC)
cross@spitfire.i.gajendra.net (Dan Cross) wrote:
In article <20261005224717.00004719@yahoo.com>,
Michael S <already5chosen@yahoo.com> wrote:
On Mon, 5 Oct 2026 10:52:28 -0400=20
Arne Vajh=F8j <arne@vajhoej.dk> wrote:
=20
On 10/5/2026 10:44 AM, Arne Vajh=F8j wrote:
And in case someone is interested in VMS then it is:
=20
100 ns units since 1858 internally and 32 bit unsigned
time_t.
=20
So VMS has a 2106 problem not a 2038 problem. =20
I can not figure out what you have in mind. =20
He's referring to when VMS's `time_t` rolls over. Since it is
an unsigned 32-bit int, overflow will be in 2106, not 2038, as
in the case for signed 32-bit `time_t` on other systems.
=20
What I didn't get is how the problem related to 1858.
Now I understand that it is not related.
Peripherally related, perhaps. The baseline for VMS
time is 17 November 1858 00:00:00.
For Vax basic users, it was 1970, so we had to fix it before 2003 - we
did it with Y2K
That seems strange, unless you were running your BASIC
interpreter on UnixV32 or BSD (the unix epoch started
Dec 31, 1969 at midnight).
TIME function in VSI BASIC seems to have been 'number of seconds since midnight' as
a floating point value. I mainly used Macro32, Bliss32 and VAX Pascal, where I had access
to the VMS starlet functions for time management and inquiry.
VSI BASIC Returns
0 The amount of time elapsed since midnight in seconds
1 The CPU time of the current process in tenths of a second
2 The connect time of the current process in minutes
TIME$ returns a string with the current time.
Our dates were stored as Julian dates
Chris Townley <news@cct-net.co.uk> writes:
On 07/10/2026 23:14, Scott Lurndal wrote:
Chris Townley <news@cct-net.co.uk> writes:
On 07/10/2026 21:54, Scott Lurndal wrote:
Michael S <already5chosen@yahoo.com> writes:
On Wed, 7 Oct 2026 11:58:27 -0000 (UTC)
cross@spitfire.i.gajendra.net (Dan Cross) wrote:
In article <20261005224717.00004719@yahoo.com>,
Michael S <already5chosen@yahoo.com> wrote:
On Mon, 5 Oct 2026 10:52:28 -0400=20
Arne Vajh=F8j <arne@vajhoej.dk> wrote:
=20
On 10/5/2026 10:44 AM, Arne Vajh=F8j wrote:
And in case someone is interested in VMS then it is:
=20
100 ns units since 1858 internally and 32 bit unsigned
time_t.
=20
So VMS has a 2106 problem not a 2038 problem. =20
I can not figure out what you have in mind. =20
He's referring to when VMS's `time_t` rolls over. Since it is
an unsigned 32-bit int, overflow will be in 2106, not 2038, as
in the case for signed 32-bit `time_t` on other systems.
=20
What I didn't get is how the problem related to 1858.
Now I understand that it is not related.
Peripherally related, perhaps. The baseline for VMS
time is 17 November 1858 00:00:00.
For Vax basic users, it was 1970, so we had to fix it before 2003 - we >>>> did it with Y2K
That seems strange, unless you were running your BASIC
interpreter on UnixV32 or BSD (the unix epoch started
Dec 31, 1969 at midnight).
TIME function in VSI BASIC seems to have been 'number of seconds since midnight' as
a floating point value. I mainly used Macro32, Bliss32 and VAX Pascal, where I had access
to the VMS starlet functions for time management and inquiry.
VSI BASIC Returns
0 The amount of time elapsed since midnight in seconds
1 The CPU time of the current process in tenths of a second
2 The connect time of the current process in minutes
TIME$ returns a string with the current time.
Our dates were stored as Julian dates
Not uncommon in the mainframe days. Did you use 5 or 7 digit
values? (YYDDD or YYYYDDD)
On 08/10/2026 16:50, Scott Lurndal wrote:
Chris Townley <news@cct-net.co.uk> writes:
On 07/10/2026 23:14, Scott Lurndal wrote:
Chris Townley <news@cct-net.co.uk> writes:
Our dates were stored as Julian dates
Not uncommon in the mainframe days. Did you use 5 or 7 digit values?
(YYDDD or YYYYDDD)
Dates were Julian dates, Year starting 01-Jan-1970 X 1000, plus days
and stored as signed word - Basic doesn't do unsigned integers
Chris Townley <news@cct-net.co.uk> writes:
On 08/10/2026 16:50, Scott Lurndal wrote:
Chris Townley <news@cct-net.co.uk> writes:
On 07/10/2026 23:14, Scott Lurndal wrote:
Chris Townley <news@cct-net.co.uk> writes:
[ massive snippage ]
Our dates were stored as Julian dates
Not uncommon in the mainframe days. Did you use 5 or 7 digit values?
(YYDDD or YYYYDDD)
Dates were Julian dates, Year starting 01-Jan-1970 X 1000, plus days
and stored as signed word - Basic doesn't do unsigned integers
That's not "Julian dates". Julian dates are an integer number of days since >the beginning of the Julian epoch (12:00 noon, 1 January 4713 Julian =
24 November 4714 Gregorian) + the fraction of a day since the beginning of the >Julian day.
Rich Alderson <news@alderson.users.panix.com> writes:
That's not "Julian dates". Julian dates are an integer number of days since >> the beginning of the Julian epoch (12:00 noon, 1 January 4713 Julian =
24 November 4714 Gregorian) + the fraction of a day since the beginning of >> the Julian day.
Technically speaking, perhaps. In reality, such notations were commonly _called_ Julian dates in computing during the 1960s through Y2K.
Michael S <already5chosen@yahoo.com> writes:
On Wed, 7 Oct 2026 11:58:27 -0000 (UTC)
cross@spitfire.i.gajendra.net (Dan Cross) wrote:
In article <20261005224717.00004719@yahoo.com>,
Michael S <already5chosen@yahoo.com> wrote:
On Mon, 5 Oct 2026 10:52:28 -0400=20
Arne Vajh=F8j <arne@vajhoej.dk> wrote:
=20
On 10/5/2026 10:44 AM, Arne Vajh=F8j wrote:
And in case someone is interested in VMS then it is:
=20
100 ns units since 1858 internally and 32 bit unsigned
time_t.
=20
So VMS has a 2106 problem not a 2038 problem. =20
I can not figure out what you have in mind. =20
He's referring to when VMS's `time_t` rolls over. Since it is
an unsigned 32-bit int, overflow will be in 2106, not 2038, as
in the case for signed 32-bit `time_t` on other systems.
=20
What I didn't get is how the problem related to 1858.
Now I understand that it is not related.
Peripherally related, perhaps. The baseline for VMS
time is 17 November 1858 00:00:00.
I did not read the article, but from citation it sounds that they are
talking about default C RTL DLLs supplied with the OS, most likely msvcr120.dll, rather than about OS itself.
As mentioned by few posters above, Windows native time format (FILETIME)
is identical in 32-bit and 64-bit OS variants. It is going to overflow
in 308th century AC. So it does not sound like a problem that even the youngest among us should be concerned about.
On 10/7/2026 4:54 PM, Scott Lurndal wrote:
Michael S <already5chosen@yahoo.com> writes:
Peripherally related, perhaps. The baseline for VMS
time is 17 November 1858 00:00:00.
In what time zone?
:-)
On 10/7/2026 4:54 PM, Scott Lurndal wrote:
Michael S <already5chosen@yahoo.com> writes:
On Wed, 7 Oct 2026 11:58:27 -0000 (UTC)
cross@spitfire.i.gajendra.net (Dan Cross) wrote:
In article <20261005224717.00004719@yahoo.com>,
Michael S-a <already5chosen@yahoo.com> wrote:
On Mon, 5 Oct 2026 10:52:28 -0400=20
Arne Vajh=F8j <arne@vajhoej.dk> wrote:
=20
On 10/5/2026 10:44 AM, Arne Vajh=F8j wrote:
And in case someone is interested in VMS then it is:
=20
100 ns units since 1858 internally and 32 bit unsigned
time_t.
=20
So VMS has a 2106 problem not a 2038 problem. =20
I can not figure out what you have in mind. =20
He's referring to when VMS's `time_t` rolls over.-a Since it is
an unsigned 32-bit int, overflow will be in 2106, not 2038, as
in the case for signed 32-bit `time_t` on other systems.
=20
What I didn't get is how the problem related to 1858.
Now I understand that it is not related.
Peripherally related, perhaps.-a The baseline for VMS
time is 17 November 1858 00:00:00.
In what time zone?
:-)
Op 10.okt.2026 om 16:52 schreef Dave Froble:
On 10/7/2026 4:54 PM, Scott Lurndal wrote:
Michael S <already5chosen@yahoo.com> writes:
On Wed, 7 Oct 2026 11:58:27 -0000 (UTC)
cross@spitfire.i.gajendra.net (Dan Cross) wrote:
In article <20261005224717.00004719@yahoo.com>,
Michael S-a <already5chosen@yahoo.com> wrote:
On Mon, 5 Oct 2026 10:52:28 -0400
Arne Vajh=F8j <arne@vajhoej.dk> wrote:
On 10/5/2026 10:44 AM, Arne Vajh=F8j wrote:
And in case someone is interested in VMS then it is:
100 ns units since 1858 internally and 32 bit unsigned
time_t.
So VMS has a 2106 problem not a 2038 problem. =20
I can not figure out what you have in mind. =20
He's referring to when VMS's `time_t` rolls over.-a Since it is
an unsigned 32-bit int, overflow will be in 2106, not 2038, as
in the case for signed 32-bit `time_t` on other systems.
What I didn't get is how the problem related to 1858.
Now I understand that it is not related.
Peripherally related, perhaps.-a The baseline for VMS
time is 17 November 1858 00:00:00.
In what time zone?
:-)
The local time zone. Initially VMS did not know about time zones and
most sites ran the clock in the local time zone.
"Fred. Zwarts" <F.Zwarts@HetNet.nl> writes:
Op 10.okt.2026 om 16:52 schreef Dave Froble:
On 10/7/2026 4:54 PM, Scott Lurndal wrote:
Michael S <already5chosen@yahoo.com> writes:
On Wed, 7 Oct 2026 11:58:27 -0000 (UTC)
cross@spitfire.i.gajendra.net (Dan Cross) wrote:
In article <20261005224717.00004719@yahoo.com>,
Michael S-a <already5chosen@yahoo.com> wrote:
On Mon, 5 Oct 2026 10:52:28 -0400
Arne Vajh=F8j <arne@vajhoej.dk> wrote:
On 10/5/2026 10:44 AM, Arne Vajh=F8j wrote:
And in case someone is interested in VMS then it is:
100 ns units since 1858 internally and 32 bit unsigned
time_t.
So VMS has a 2106 problem not a 2038 problem. =20
I can not figure out what you have in mind. =20
He's referring to when VMS's `time_t` rolls over.-a Since it is
an unsigned 32-bit int, overflow will be in 2106, not 2038, as
in the case for signed 32-bit `time_t` on other systems.
What I didn't get is how the problem related to 1858.
Now I understand that it is not related.
Peripherally related, perhaps.-a The baseline for VMS
time is 17 November 1858 00:00:00.
In what time zone?
:-)
The local time zone. Initially VMS did not know about time zones and
most sites ran the clock in the local time zone.
That's a failing of VMS systems management. In TOPS-20 and TENEX, timezones >were built into the monitor, so that NOT setting the local timezone was an >error. I can't imagine that that was not true of VMS, but I've been surprised >there before.
Initially VMS did not know about time zones and most sites ran the
clock in the local time zone.
Was it really such a radical idea to keep system time internally in
(what was then GMT, later became) UTC? Seems it was, since other
systems were in no hurry to copy the concept. Even Microsoft Windows
remains prone to off-by-one-hour bugs being triggered around
daylight-saving shifts, to this day.
And in case someone is interested in VMS then it is:
100 ns units since 1858 internally and 32 bit unsigned time_t.
So VMS has a 2106 problem not a 2038 problem.
| Sysop: | Amessyroom |
|---|---|
| Location: | Fayetteville, NC |
| Users: | 76 |
| Nodes: | 6 (1 / 5) |
| Uptime: | 35:14:42 |
| Calls: | 1,266 |
| Files: | 1,362 |
| D/L today: |
3 files (6,742K bytes) |
| Messages: | 284,775 |