Page 1 of 1

Year 2038 problem !

Posted: Sat Nov 04, 2017 7:26 pm
by Adcock
Currently ReactOS is a 32 bit OS.(mostly)
Have ReactOS developers already gotten rid of Year 2038 problem?

Re: Year 2038 problem !

Posted: Sat Nov 04, 2017 8:12 pm
by hbelusca
This is a unix-only problem, therefore doesn't concern us.

Re: Year 2038 problem !

Posted: Sun Nov 05, 2017 2:59 pm
by Adcock
Well 32 bit Windows will be affected.
However, by then ReactOS will be at least 128 bit. Maybe 256 bit too.
So, this was an useless question.
Sorry.

Re: Year 2038 problem !

Posted: Sun Nov 05, 2017 6:09 pm
by hbelusca
Adcock wrote:Well 32 bit Windows will be affected.
Nope, because internally Windows does not use a 32-bit number to store the number of seconds.

Re: Year 2038 problem !

Posted: Sun Nov 05, 2017 7:19 pm
by Adcock
hbelusca wrote:
Adcock wrote:Well 32 bit Windows will be affected.
Nope, because internally Windows does not use a 32-bit number to store the number of seconds.
Hmmm...Didn't know that!
As of now MS Windows is still closed source.
Thanks for the information.

Hey. You guys are Windows geek.
Why not write a Windows/ReactOS internals or Inside ReactOS?
Please make that book freely available when you make it.
(free means libre and cost free) :D

Re: Year 2038 problem !

Posted: Sun Nov 05, 2017 11:08 pm
by erkinalp
There is Windows Internals by Mark Russinovich and Alex Ionescu.

Re: Year 2038 problem !

Posted: Mon Nov 06, 2017 12:51 pm
by middings
Adcock, look up the documentation of the time functions used by Microsoft's versions of Windows. Time is kept as a 64-bit value that represents the number of 100-nanosecond intervals since January 1, 1601 (UTC). This is true even for versions of Windows for 32-bit processors. A roll-over of this 64-bit value will not occur before the year 30,827 A.D. ReactOS will be able to operate "in the year 2525, if man is still alive; if woman can survive..."

However, some applications that are run under Windows might use their own method of time keeping instead of the Windows time keeping functions. Some file systems cannot store file time (e.g., creation date, date last accessed, or date modified) with values as large as Windows can. Those applications and file systems might be vulnerable to something like the Year 2038 Problem.

Re: Year 2038 problem !

Posted: Mon Nov 06, 2017 3:17 pm
by Adcock
erkinalp : Thanks.
But that/those book/s is/are not free of cost.

middings : Thanks.
Are you sure the same is applicable for MS Windows XP?

And Oh, yes. You guys are geek too.
Please release a book of that kind for free (of cost).
A totally libre book of that kind would be super handy. :|

Re: Year 2038 problem !

Posted: Mon Nov 06, 2017 8:37 pm
by ekohl
Adcock wrote:middings : Thanks.
Are you sure the same is applicable for MS Windows XP?
Yes, because the higher-level time functions call NtQuerySystemTime (https://msdn.microsoft.com/de-de/librar ... s.85).aspx) to retrieve the current system time.

Re: Year 2038 problem !

Posted: Tue Nov 07, 2017 6:08 am
by ROCKNROLLKID
Adcock wrote:Well 32 bit Windows will be affected.
However, by then ReactOS will be at least 128 bit. Maybe 256 bit too.
So, this was an useless question.
Sorry.
To be honest, I doubt there will ever be a 256-bit. 64bit is already around 16 - 17 exibibytes. 128bit would be 281,474,976,710,656 yobibytes. The more important issue now with ram limits is what MS sets it for Windows. For example, Windows XP 64-bit had a limit of only 128gb of ram. This applied to Vista and 7 for pro/ultimate/business editions, until they later patched it to 192gb. Win10 apparently allows up to 2TB, except for home edition, which is at 128gb.

Not sure what ReactOS has plans to do with the ram limits for when they do a 64-bit version, but I don't think they should follow the same policy.

Re: Year 2038 problem !

Posted: Tue Nov 07, 2017 7:10 am
by Adcock
ROCKNROLLKID : You are right.
64 bit was created because it was needed.
It was also economically benficial.
As of now 64 bit system with multi processor and multi core combination meets all requirements.
Normal people won't break 64 bit's limits so easily.
However scientific community might require 128 bit.
For scientific research it is not about power or limits.
It's about speed.
But in this case you are right.

Re: Year 2038 problem !

Posted: Tue Nov 07, 2017 8:13 pm
by Konata
This blatantly misinformed and baseless fear about one subject being flawed just because another vaguely-related subject is flawed reminds me of the Dihydrogen monoxide hoax.

Re: Year 2038 problem !

Posted: Tue Nov 07, 2017 8:52 pm
by hbelusca
Konata wrote:[...] reminds me of the Dihydrogen monoxide hoax.
... or how to give complicated names to water xD

Re: Year 2038 problem !

Posted: Wed Nov 08, 2017 6:07 pm
by erkinalp
Konata wrote:how to give complicated names to water
Dihydrogen monoxide hoax is a campaign to prohibit water.