4 ms·
Probably will crash if you told it correctly. You know, the old Y2K problem. ;-)
by cpr 10y ago
Probably will crash if you told it correctly. You know, the old Y2K problem. ;-)
- byebyetech 10y agoYup, It will overflow its mind!
- colejohnson66 10y agoAs someone who was too young at the time, why would it crash? I thought the Y2K problem was just programs only storing the last two digits. So 2016 would be stored as 16 and displayed as 1916.
- djsumdog 10y agoYep, that's pretty much it. You could run into crashes if something was dependent on the date being in the future since when the machine was built (and hence you get a negative number when you shouldn't have), or if the machine was alive between 1999 and 2000 (in which case the BIOS or applications may complain because you've gone back in time). This /mostly/ affected date formats. Well built systems and programs measured time in seconds since the epoch on operating systems that supported that time representation format.
- dfox 10y agoMany RTC chips used in PC's behaved weirdly when set to any year >2000 (resp. <80 or so). These behaviors included setting year to some fixed value, setting it to correct value but not incrementing date ever again and so on.