Y3k issues

No worries, hopefully that's enough time for even Microsoft to fix it. Besides, we should be at least up to Windows 11 or 12 by then.
 
You all should be far more aware of the year 2038 problem, it afflicts far more things than Windows.

But no matter what, there's always a constraint on how large a variable can get, no matter what design you use, there will always be an "end" date.
 
Worrying about this sort of potential issue, 80 years in the future, and basing that worry on the technology of today, well - foolish.

The article, however, makes it clear that this is not really the concern. It's a bizarre and unlikely, but not impossible, confluence of circumstances that are.
 
Worrying about this sort of potential issue, 80 years in the future, and basing that worry on the technology of today, well - foolish.

The article, however, makes it clear that this is not really the concern. It's a bizarre and unlikely, but not impossible, confluence of circumstances that are.

Its not 80 years in the future you have to worry about if the bios date is wrong say by accident you selected 3020 windows will fail to load so that effects us now not to mention someone could make malware that changes your bios date causing windows 10 crash.
 
Its not 80 years in the future you have to worry about if the bios date is wrong say by accident you selected 3020 windows will fail to load so that effects us now not to mention someone could make malware that changes your bios date causing windows 10 crash.

So which part of my comment, "The article, however, makes it clear that this is not really the concern. It's a bizarre and unlikely, but not impossible, confluence of circumstances that are," doesn't already acknowledge that?
 
Perhaps the year 3,000 will be the year of Linux on the desktop?

Did you miss my post above? All *nix dies in 2038, that's the Epoc Problem... and you can use it to screw up *nix boxes now.

Anyone freaking out because someone with admin rights played with the system clock to cause a problem, is already being stupid because they aren't freaking out about the correct thing... the fact that someone other than the owner has admin rights.

And in the case of mobile devices, the fact that law abiding owners can't actually have admin rights, whereas the bad guys do... the fight was lost before it started.
 
@Computer Bloke, it's the embedded systems that are the problem though... all those printers, routers, switches, cameras, and who knows what else.

It's not going to end the world in any meaningful way, just basically make our phones explode late Jan 2038.

The desktops / laptops / servers will be updated to software automatically to deal with this. Honestly, I foresee this largely being a problem with smart phones, especially Android based ones if Google doesn't get ahead of the lack of updates problem for those platforms.
 
The issue doesn't have to be 980 years in the future, you just have to have access to set the system clock to think it's 980 years in the future.

Which of course means you need admin rights... and therefore already own the system anyway.
 
Guys. Y2K was real!
A fellow who lived across the road from me told me he lost a shoe at "exactly midnight 1999/2000,"
That shoe was never seen again. Maybe its in the future?
The lady next door had a cat that fell ill and had to be put to sleep....at 5 minutes to midnight 1999!
Damn Y2K again...
 
New Guys. Y2K was real!
Most folks never heard that it took down 2 power generating stations in the US, which wasn't enough to cause any trouble for the power grid, which is why most never heard about it. It could've been much worse, had many $billions not been spent by large corporations and governments to fix problem systems.

I didn't personally see any Y2K problems with computers, but my own machine at the time had a Y2.001K problem. The first time I turned it on after 1/1/2001, it choked and wouldn't boot until I set the clock to before 1/1/2001. It worked fine that way until I got a new machine set up. Still have that machine buried in a box somewhere.
 
Back
Top