Urgent: First Y2.1K Embedded System Problem Identified (humor)greenspun.com : LUSENET : Electric Utilities and Y2K : One Thread |
As you know, I frequently ask for manufacturer/model numbers when claims are made concering embedded device "hard failures" (failure to function).In fairness therefore, I will supply this information and even a link to my extraordinary claim of being the first World Reknowned Embedded System Y2.1K Expert to identify a Year 2100 problem:
Fortunately, this will not cause the device to malfunction, but the date will have to be manually set. You are hereby forewarned.
Regards,
-- Anonymous, August 17, 1999
That's some sense of humor. Was trying to think of what else you might find funny. The scores of non-compliant product cycles listed in detail on Lucent's, Motorola's, et. all's web pages perhaps. Needed something a little closer to the electric industry though. Here's another good one for you. The punchline on this one happens a bit earlier though.Honywell lists the compliance status of it's industry related products at
http://www.honeywell.com/year2000/IAC/Readiness.stm
If you download the excel spreadsheet look at row 257: Product: SCADA Version: All Ready Status: N Customer Action/Comment: No plans to test. No replacement.
Maybe N stands for Nominal, huh.
-- Anonymous, August 18, 1999
Let's try that again.Product: SCADA
Version: ALL
Ready Status: N
Customer Action/Comment: No plans to test. No replacement
-- Anonymous, August 18, 1999
joke received on this end :>)
-- Anonymous, August 21, 1999