Microsoft has changed time

[Stupiduser]

Microsoft Exchange is broken due to 32bit date format not being able to handle timecodes "larger" than the "number" 2147M in binary. 

 

 

Quotes

Quote

 

 

My thoughts

Y2K was preventable because of advanced warning that allowed us to reprogram vulnerable systems to have four year digits. Then a simple database script added 19 in front of all year entries in our databases. That is not as easy these days because systems have so much more data that is timecoded. So microsoft is proposing is that we change TIME. They have implemented a fix that just adds 48 months to the current timeline. Kicking the issue down the road four years. Microsoft is calling today the 8th day of the 13th month of 2021. They literally have changed TIME. Then they added a translator to the engine. If they can't fix this by then the issue will repeat. If they convert from YYYYMMDD to MMDDYYYY they would have unlimited time codes until the year 10000. They can't change the format or all previous entries will be lost, because the system are so redundant and cannot go offline long enough to fix all previous entries. 

 

What other systems use the same 32bit timecoding? Banking? Crypto? IRS?

 

Sources

https://docs.microsoft.com/en-us/answers/questions/680488/microsoft-exchange-fip-fs-scan-engine-failed-to-lo.html

[Guest]

 

[paddy-stone]

Already posted  

 

[paddy-stone]

1 minute ago, Nayr438 said:

 

Ah dammit, while I was searching for the already posted topic you beat me to it