From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=0.6 required=5.0 tests=BAYES_20,INVALID_MSGID
	autolearn=no autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,92471489ebbc99c6
X-Google-Attributes: gid103376,public
From: eachus@spectre.mitre.org (Robert I. Eachus)
Subject: Re: Y2K Issues
Date: 1998/11/04
Message-ID: <EACHUS.98Nov4181012@spectre.mitre.org>#1/1
X-Deja-AN: 408470009
References: <362B53A3.64E266AB@res.raytheon.com> <362B8D2F.802F42E6@lmco.com>
 <710nnc$jop@felix.seas.gwu.edu> <713nvs$cv8$1@nnrp1.dejanews.com>
 <71acr3$do4$1@husk.cso.niu.edu> <363E5AAC.E2F0AB7D@flinet.com>
Organization: The Mitre Corp., Bedford, MA.
Newsgroups: comp.lang.ada
Date: 1998-11-04T00:00:00+00:00
List-Id: <comp.lang.ada>

In article <363E5AAC.E2F0AB7D@flinet.com> Marin David Condic <diespammer@flinet.com> writes:

   > Who was aware of the Y2K problem before 1995? 1990?  1985? 1980? 1975?
   >
   > Who was aware of the Y2K problem as it affects embedded programs before
   > 1995? 1990?  1985? 1980? 1975?

   There are a lot of people who were aware of the Y2K problem in the
late sixties, and it is very embarrassing that a lot of banks who
fixed their loan software in time for 1970 (for thirty year mortages)
failed to take the lesson to heart and require that any new software
be Y2K compliant back then.

   Incidently just to rub it in, OS360 had a millenial bug that was a
decade bug--the year was internally stored as one decimal digit, and
OS360 would fail to boot if it overflowed.  This was fixed in the
English language versions in plenty of time, but some of the European
versions were not ready for January 1, 1970.





--

					Robert I. Eachus

with Standard_Disclaimer;
use  Standard_Disclaimer;
function Message (Text: in Clever_Ideas) return Better_Ideas is...