Oddbean new post about | logout
▲ ▼
e3f20df3 | 1 years ago (raw) | root | parent | reply | flag 
 @e7cebe76 @60d98082 this gear had no date function. it had no time/date clock. most transmission systems were PDH and implemented in hardware.

like you, we wrote to all suppliers for certificates of compliance. i don't think we shutdown anything.
▲ ▼
Mark :verified: | 1 years ago (raw) | root | parent | reply | flag 
 @d8402a8b @60d98082 
Yeah - that was likely in lower end network gear. I could see some higher end gear would use date/time in some way (say for updates or NTP services).

Hey - my favorite one was the request to a company for their Y2K certification for SAND.
▲ ▼
e3f20df3 | 1 years ago (raw) | root | parent | reply | flag 
 @e7cebe76 @60d98082 had to be a joke
▲ ▼
Mark :verified: | 1 years ago (raw) | root | parent | reply | flag 
 @d8402a8b @60d98082 
Alas, no.

It was one of those - ALL companies must respond with their certification statement about their products being compatible with Y2K.

I did a quick search - I can't seem to find an online source for that.

I will also note that Y2K problems started in 1995 or so - in credit card processing when the expiration date of the card was 2000 or later.

They continue to pop up in 2010, 2020 (y2k+20) where code worked around the problem instead of fixing it too.
▲ ▼
e3f20df3 | 1 years ago (raw) | root | parent | reply | flag 
 @e7cebe76 @60d98082 
i still don't believe that.

inspired by y2k, i made a y2026 (i think) bug in a lotus notes system i wrote. 

when year is 2026 it would pop up a dialogue box expressing amazement that this code was still in use and that we had run out of letters of alphabet: A was year 2000 from memory.

i was told it was removed when i left.
▲ ▼
e3f20df3 | 1 years ago (raw) | root | parent | reply | flag 
 @e7cebe76 @60d98082 
no software in these beasts - just chips and hard coded logic.

later version had software for configuration, but this didn't drive operation.

odd. can't find any pictures