19 January 2038 - Unix Millennium Bug

Anybody tried to change the system date to: 19th January, 2038? It's
worth a try to see if "Unix Millennium Bug" affects Windows 10 systems.
After changing the time, reboot the machine and use it for a few days to
see if there are problems apart from Anti-virus definitions becomes out
of date!!!

PLEASE DON'T DO THIS ON YOUR PRODUCTION/MAIN MACHINE OTHERWISE YOU'LL
BLAME ME FOR BEING A BAD GUY!!!!!!!

https://www.youtube.com/watch?v=brZEd-8bt68




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

Good Guy wrote:

Anybody tried to change the system date to: 19th January, 2038? It's
worth a try to see if "Unix Millennium Bug" affects Windows 10 systems.
After changing the time, reboot the machine and use it for a few days to
see if there are problems apart from Anti-virus definitions becomes out
of date!!!

PLEASE DON'T DO THIS ON YOUR PRODUCTION/MAIN MACHINE OTHERWISE YOU'LL
BLAME ME FOR BEING A BAD GUY!!!!!!!

https://www.youtube.com/watch?v=brZEd-8bt68

It shouldn't, since Windows isn't any variety of Unix and has its own epoch
(several, really, depending on what you're talking about) with system dates
apparently supported through the year 30,828. See these Wikipedia articles:

https://en.wikipedia.org/wiki/System...rating_systems
https://en.wikipedia.org/wiki/Time_f...d_storage_bugs

On the other hand, I'm not willing to try it... just in case.

--
We need a true leader, not a crown.

On Mon, 7 Aug 2017 05:46:41 +0100, Good Guy
wrote:


Anybody tried to change the system date to: 19th January, 2038? It's
worth a try to see if "Unix Millennium Bug" affects Windows 10 systems.
After changing the time, reboot the machine and use it for a few days to
see if there are problems apart from Anti-virus definitions becomes out
of date!!!

PLEASE DON'T DO THIS ON YOUR PRODUCTION/MAIN MACHINE OTHERWISE YOU'LL
BLAME ME FOR BEING A BAD GUY!!!!!!!

https://www.youtube.com/watch?v=brZEd-8bt68

Using a 64-bit OS eliminates the problem. People might still be using
32-bit Windows today, but I doubt that they still will in twenty
years.

--
Doomsdrzej
EFF & OpenMedia member,
TheRebel.media & Infowars supporter

Linux: The Chrysler of operating systems.

On 7/8/2017 11:59 PM, Doomsdrzej wrote:

Using a 64-bit OS eliminates the problem. People might still be using
32-bit Windows today, but I doubt that they still will in twenty
years.

I believe most business applications are still using 32-bit date-time
data types ... especially small companies.

--
@~@ Remain silent! Drink, Blink, Stretch! Live long and prosper!!
/ v \ Simplicity is Beauty!
/( _ )\ May the Force and farces be with you!
^ ^ (x86_64 Ubuntu 9.10) Linux 2.6.39.3
�借貸! ��騙! ��交! �打交! �打劫! �自殺! 請考慮綜� (CSSA):
http://www.swd.gov.hk/tc/index/site_...sub_addressesa

On 7/8/2017 12:46 PM, Good Guy wrote:

Anybody tried to change the system date to: 19th January, 2038? It's
worth a try to see if "Unix Millennium Bug" affects Windows 10 systems.
After changing the time, reboot the machine and use it for a few days to
see if there are problems apart from Anti-virus definitions becomes out
of date!!!

PLEASE DON'T DO THIS ON YOUR PRODUCTION/MAIN MACHINE OTHERWISE YOU'LL
BLAME ME FOR BEING A BAD GUY!!!!!!!

https://www.youtube.com/watch?v=brZEd-8bt68

Test Office 2007! I think it's a 32-bit application. I suspect many old
Office documents are still using 32-bit data types.

--
@~@ Remain silent! Drink, Blink, Stretch! Live long and prosper!!
/ v \ Simplicity is Beauty!
/( _ )\ May the Force and farces be with you!
^ ^ (x86_64 Ubuntu 9.10) Linux 2.6.39.3
�借貸! ��騙! ��交! �打交! �打劫! �自殺! 請考慮綜� (CSSA):
http://www.swd.gov.hk/tc/index/site_...sub_addressesa