Page 1 of 2

Year 2038 problem

Posted: Fri Jan 26, 2018 10:34 pm
by AdrianGlowacki
Welcome whether will Reactos have a problem on January 19, 2038 or no? Whether ReactOS using 32 bit time?

Re: Year 2038 problem

Posted: Fri Jan 26, 2018 10:41 pm
by Fraizeraust
Based from my current knowledge, Windows doesn't use a signed 32-bit integer to store the timestamp so the problem doesn't concern us whatsoever. There was a topic before that users discussed about this, maybe it is in the Off-Topic section.

Re: Year 2038 problem

Posted: Sat Jan 27, 2018 12:09 am
by karlexceed

Re: Year 2038 problem

Posted: Sat Jan 27, 2018 6:52 am
by middings
Thank you for the link, karlexceed.

The original poster (OP) should have performed a search of the forums for "2038" before posting.

Re: Year 2038 problem

Posted: Sat Jan 27, 2018 8:54 am
by Konata
This isn't a "Year 2038" problem, it's a "Linux developers are dumb as bricks" problem, every other Unix hardened against this about a decade before Linux did, and of course Windows has always used 64-bit time.
I love it when the world panics over Linux being garbage, you'd think they'd learn by now. At least Sony did the right thing using FreeBSD for the PS4.

Re: Year 2038 problem

Posted: Sun Jan 28, 2018 12:13 am
by AdrianGlowacki
I do not know. Others write something else that the problem of the year also has windows (only 32 bit) and on the other hand actually writes here https://en.wikipedia.org/wiki/Epoch_%28 ... ce_date%29 that the time of Windows begins on 1 January 1601 so I do not know . Now I'm lost in all this. :?:

Re: Year 2038 problem

Posted: Sun Jan 28, 2018 1:18 am
by middings
AdrianGlowacki wrote:I do not know. Others write something else that the problem of the year also has windows (only 32 bit) and on the other hand actually writes here https://en.wikipedia.org/wiki/Epoch_%28 ... ce_date%29 that the time of Windows begins on 1 January 1601 so I do not know . Now I'm lost in all this. :?:
AdrianGlowaki, the '32' of 32-bit Microsoft Windows or ReactOS refers to the length of the address pointers used by the operating system. The '32' is not a limitation of the length in bits of a piece of internal data used by the operating system or application programs. Even the now-obsolete 16-bit Windows (such as Microsoft Windows 3.1) could keep time using 64 bits.

Re: Year 2038 problem

Posted: Sun Jan 28, 2018 9:17 am
by Konata
AdrianGlowacki wrote:I do not know. Others write something else that the problem of the year also has windows (only 32 bit) and on the other hand actually writes here https://en.wikipedia.org/wiki/Epoch_%28 ... ce_date%29 that the time of Windows begins on 1 January 1601 so I do not know . Now I'm lost in all this. :?:
You should probably actually learn about this stuff instead of screaming "the world is ending in the year 2000 because of all the broken computers". And maybe stop listening to whatever morons are telling you that a computer can't represent data larger than it's bus size.

Re: Year 2038 problem

Posted: Sun Jan 28, 2018 12:36 pm
by Forever Winter
Konata wrote:You should probably actually learn about this stuff instead of screaming "the world is ending in the year 2000 because of all the broken computers". And maybe stop listening to whatever morons are telling you that a computer can't represent data larger than it's bus size.
And you should stop being such an arrogant asshole.

[Edited to avoid misunderstandings]

Re: Year 2038 problem

Posted: Sun Jan 28, 2018 1:56 pm
by AdrianGlowacki
Konata wrote:
AdrianGlowacki wrote:I do not know. Others write something else that the problem of the year also has windows (only 32 bit) and on the other hand actually writes here https://en.wikipedia.org/wiki/Epoch_%28 ... ce_date%29 that the time of Windows begins on 1 January 1601 so I do not know . Now I'm lost in all this. :?:
You should probably actually learn about this stuff instead of screaming "the world is ending in the year 2000 because of all the broken computers". And maybe stop listening to whatever morons are telling you that a computer can't represent data larger than it's bus size.
I do not shout only I'm interested in the problem of 2038 year.
Forever Winter wrote:And you should stop being such an arrogant asshole.
I'm not an arrogant asshole!

Re: Year 2038 problem

Posted: Sun Jan 28, 2018 2:52 pm
by Forever Winter
AdrianGlowacki wrote:I'm not an arrogant asshole!
My post was directed at Konata, not at you.

Re: Year 2038 problem

Posted: Sun Jan 28, 2018 2:56 pm
by AdrianGlowacki
Forever Winter Ops Sorry :(

Re: Year 2038 problem

Posted: Sun Jan 28, 2018 3:28 pm
by AdrianGlowacki
I have one more question, what does "AD 30,828" mean? At https://en.wikipedia.org/wiki/System_time, he writes that Windows has its beginning and the end of time from January 1, 1601 to AD 30,828. In which day, month, year and at what time does the Windows era end?

Re: Year 2038 problem

Posted: Sun Jan 28, 2018 3:31 pm
by verserk
Konata wrote:This isn't a "Year 2038" problem, it's a "Linux developers are dumb as bricks" problem, every other Unix hardened against this about a decade before Linux did, and of course Windows has always used 64-bit time.
I love it when the world panics over Linux being garbage, you'd think they'd learn by now. At least Sony did the right thing using FreeBSD for the PS4.
Jeez, tell us how you really feel...

Re: Year 2038 problem

Posted: Sun Jan 28, 2018 4:21 pm
by val
smells like a couple of linuxoids had expereinced a bit of butthurt, :D
by the way, "arrogant asshole" - this is an exact definition of a linux kernel developer. isn't it?

there is no such a problem, that's the answer, Adrian, be happy. The galaxy is not endangered. :)