
	Where results make sense

Topic: Year 2000 problem

	Year 2000 problem - Wikipedia, the free encyclopedia
		The Year 2000 problem (also known as the Y2K problem, the millennium bug and the Y2K Bug) was the result of a practice in computer program design that caused some date-related processing to operate incorrectly for dates and times on and after January 1, 2000.
		Y2K was the common abbreviation for the year 2000 problem.
		Another related problem for the year 2000 was that it was a leap year even though years ending in "00" are normally not leap years.
	en.wikipedia.org /wiki/Year_2000_problem (4503 words)

	Year 2000 problem - Wikipedia
		The Year 2000 Problem was a flaw in computer program design that caused some date-related processing to operate incorrectly for dates and times after January 1, 2000.
		It was thought computer programs could stop working or produce erroneous results because they stored years with only two digits and that the year 2000 would be represented by '00' and would not follow 1999 (i.e., '99') in numerical sequence.
		Y2K was the common slang for the year 2000 problem.
	nostalgia.wikipedia.org /wiki/Y2K (1097 words)

	What is the Year 2000 Problem (Site not responding. Last check: 2007-10-23)
		To reflect the year in a program, many computers only have fields for the last two digits to represent the year, assuming that the first two digits are '19', e.g.
		Further complicating the problem is the fact that the Year 2000 is a leap year.
		As the year 2000 approaches, these computers and programs will see the year as 00 or 1900, which is the root of the problem.
	www.nmsu.edu /y2k/y2kproblem.html (745 words)

	Year 2000 problem. The Columbia Encyclopedia, Sixth Edition. 2001-05
		In the 1960s and 70s programmers who designed computer systems dropped the first two digits of a year when storing or processing dates to save what then was expensive and limited memory; such a system records the year 2000 as 00 and cannot distinguish it from 1900.
		In sorting, comparison, and arithmetic operations, the year 2000 would be treated as if it were equivalent to 0 rather than 100, causing incorrect results.
		Because their designers expected such computer systems to be replaced before the beginning of the year 2000, using a two-digit date was not regarded as a problem.
	www.bartleby.com /65/ye/Year2000.html (275 words)

	Y2K: YEAR 2000 PROBLEM
		The year 2000 date problem was inadvertently created in the late 1950s and early 1960s-the early days of computers and computer programming.
		The "millennium bug" as the date problem is popularly referred to, resulted from the use of a two-digit year field in computer applications.
		Two digits, rather than four, were originally used to represent years because in the early days of computer technology, storage and memory were among the highest costs associated with using the emerging technology.
	www.martin.fl.us /GOVT/depts/isd/year2k (293 words)

	ComLinks Y2K Archives - The Year 2000 Problem
		Many developers failed to anticipate that their systems would still be in service at the Year 2000, and did not account for the millennium change.
		Now that Year 2000 is almost upon us, and it is a deadline that cannot be negotiated or avoided.
		The Year 2000 problem is not just another "technology" issue for the folks in the IT Department to sort out.
	www.comlinks.com /legal/tmjb1.htm (1088 words)

	Description of the Year 2000 Problem
		Although the three underlying problems are easy to understand and solutions are often fairly simple as well, there is no simple fix to the year 2000 issue since the use of dates and associated calculations are pervasive throughout software and that usage is not standardized.
		The principal Year 2000 problem is payback for a shortcut programmers took years ago to save on limited and extremely expensive computer memory space.
		But, unless something is done, when the year 1999 rolls over to 2000, systems that use the two-digit year field might interpret the first day of the new year as 01/01/00 and determine that "00" means 1900 with "00" coming before "99" in numerical sequence.
	www.utulsa.edu /year2000/DescriptionOfProblem.html (1068 words)

	The Year 2000 Problem in Perspective
		In the case of the Year 2000 problem, the flaw is well understood.
		Immediately after the year 2000 arrives, I suspect that almost every computer glitch that occurs anywhere in the world will be blamed on the Y2K problem, no matter the source of the problem.
		Finally, the report concludes: "The Year 2000 issue is potentially the biggest challenge ever faced by the financial industry." I guess the BIS thinks the problem is serious.
	www.aci.net /kalliste/y2000.htm (3127 words)

	FHWA - The Year 2000 Computer Problem (Site not responding. Last check: 2007-10-23)
		The roots of the Year 2000 computer problem date back to the time when data storage on computers was so expensive that it became standard practice to store only the last two digits of the year in computer systems.
		Another potential Year 2000 problem lies in operational transportation systems such as traffic signal systems run by State and local governments that may also have embedded programs in their hardware and/or software that cannnot correctly handle the Year 2000.
		FHWA's field office managers are discussing the Year 2000 readiness of these transportation systems operated by State and local governments in meetings with our external partners and customers, using Year 2000 Questions to Ask to guide their discussions.
	www.fhwa.dot.gov /y2k (537 words)

	Year 2000: The Millennium Rollover
		This works fine for years in the range 1900-1999 (on some systems this range may be limited to 1970-1999) but will yield unpredictable results when used with years outside of this range.
		Calculations based on the year value in its two digit format are likely to yield unspecified results once the value rolls over to "00" in the year 2000.
		If century is not specified, then values in the range [69-99] refer to years in the twentieth century (1969 to 1999 inclusive), and values in the range [00-68] refer to years in the twenty-first century (2000 to 2068 inclusive).
	www.unix.org /version2/whatsnew/year2000.html (1627 words)

	The Year 2000 Computer Problem (Site not responding. Last check: 2007-10-23)
		In the past, the year has been stored as a two digit data element (e.g., 96 for 1996) primarily to reduce: (1) the storage requirements of databases; (2) the processing time to run applications; and (3) the costs of data entry.
		The problem with this thinking is that a very large body of computer code developed 20-30 years ago has been maintained and modified, and is still in use today.
		The only way to be sure our applications are really year 2000 ready is to schedule and perform this kind of testing over the next year so that any necessary corrective actions (e.g., code changes, software/hardware, etc.) can be completed well before the year 2000.
	www.fhwa.dot.gov /y2k/mv2units.htm (758 words)

	The "Year 2000 Problem" (Site not responding. Last check: 2007-10-23)
		The problem seems simple enough, but solving it - and it must be solved on an inflexible deadline - will take years.
		The so-called "year 2000 problem" has perplexed banks, insurance companies, government agencies and other institutions dependent on computer data, and some analysts predict the worldwide cost of adjusting computer programs to recognize the new century could be around $650 billion.
		The problem stems from computer programs written two and three decades ago that, while still useful, never included provisions for registering the date 2000.
	www.bc.edu /bc_org/rvp/pubaf/chronicle/v5/F13/infotech.html (644 words)

	Howstuffworks "How the Year 2000 Problem Worked"
		Although the Y2K problem came and went in January of 2000, we have saved this article as an archived editon of HowStuffWorks because of its historical value.
		Published at the beginning of 1999 at the height of the Y2K panic in the media, this article is noteworthy for the sentence, "In reality, nothing will happen." In retrospect, that sentence was completely correct, but in January 1999 that was definitely not the picture the mainstream media was painting.
		In this edition of How Stuff Works we will discuss the Year 2000 problem (also known as the Y2K problem) so that you understand exactly what is happening and what is being done about it.
	computer.howstuffworks.com /y2k.htm (944 words)

	AG RVS - The Year 2000 Problem
		The Year 2000 problem is not the only DRD problem we need to worry about now.
		Another problem with the year 2000 that is not a DRD problem occurs because many programs won't recognise that the year 2000 is a leap year.
		The last point in the problem list, the lack of a standard for date representations, is not necessarily a Year 2000 problem.
	www.rvs.uni-bielefeld.de /research/Y2K/year2000.html (2614 words)

	Year 2000 Problem (Site not responding. Last check: 2007-10-23)
		Some non-compliant devices, for example, were designed to read year dates by the last two digits and thus will interpret 00 in the year 2000 as 1900.
		You should also contact your insurance company to see if any losses which might arise as a result of this problem are covered under your existing policy or, if not, whether coverage is available at a reasonable cost.
		However, the problem is well known and correctable with reasonable and diligent efforts over the coming weeks and months.
	www.gis.net /~jmullins/year2000.html (477 words)

	Reasons for the Year 2000 Problem
		The re-use of algorithms which have a hidden date processing fault is one reason why the year 2000 problem is so huge and why some people have likened it to an immense virus.
		Furthermore, because they now lack the internal resources to handle the year 2000 problem, companies who have been through BPR downsizing will be forced to outsource the Year 2000 fix project.
		With thanks to the many members of the Year 2000 mailing list, whose thoughts on this issue were invaluable while preparing this document.
	www.utbtsc.edu /infosys/year2000/why.html (2277 words)

	Year 2000 Problem Y2K y2k Millennium Bug millennia YEAR 2000 PROBLEM millenium milennium milennia bug year 2000 Y2K ...
		The Year 2000+ Software Analyzer is a program that can be used as the first step in correcting Year 2000 problems that a software package may have.
		Year 2000 problems in C Year 2000 problems in C Introduction Year 2000 problems occur because code has been written that only uses the last...
		Year 2000 NYSEG addressing the Year 2000 problem Many of the NYSEG computer systems must be modified due to certain programming limitations in recognizing dates beyond the year 1999.
	www.taxpolicy.com /year2000.htm (2975 words)

	What is Year 2000 problem? - A Word Definition From the Webopedia Computer Dictionary (Site not responding. Last check: 2007-10-23)
		This problem affects a vast amount of software, particularly accounting and database systems.
		The Year 2000 problem is sometimes referred to as the Millennium bug or Y2K problem.
		This CNN article, from January 1996, describes the various implications of changing from the year 1999 to 2000, with links to related reading.
	www.pcwebopedia.com /Year_2000_problem.htm (266 words)

	Year 2000 Problem Sightings
		Problems were said to be so frustrating that 24 of the stores closed down for anywhere from 15 minutes to almost the whole day on January 3.
		The problem appears to be an isolated one, as the same report quotes Illinois Chamber of Commerce Vice President Jim Beaumont as saying that his group had not received any reports of businesses suffering computer outages as a result of bad Y2K fixes.
		2000 January 12: A UPI report states that the problem occurred at an image processing ground station at Fort Belvoir in Virginia, and was the result of a faulty software patch intended to work around the GMT midnight transition.
	www.cv.nrao.edu /~abridle/y2k/sighting.htm (17128 words)

	The Year 2000 Problem -- Resources
		The problem with this approach is that some businesses will not be able to survive after the failure, before the fix; or for long after the fix.
		Despite the fact that total costs to remediate the problem are large, they have been spread out among industries and over years.
		Around the period of the Year 2000 transition it is expected that computer viruses will be spread by people seeking to destabilize the Internet.
	www.disastercenter.com /year2000.htm (1545 words)

	The Year 2000 problem
		2000 Aware Survey in Ireland November 1997 showed that over half of the finance directors surveyed do not have a Y2K budget and 28% have problems locating source code.
		Resource conflicts between the year 2000 and euro-currency software problems (eurocurr.doc 33K) Predicts that 35% of European applications will not be converted in time and calls for delay in EMU.
		For the majority of companies, there is a three year transition period, currency conversion only accounts for 1 or 2 FP per application, and low-impact strategies are possible.
	www.sysmod.com /year2000.htm (1483 words)

	Year 2000 Problem (Site not responding. Last check: 2007-10-23)
		The Mathematica application package contains no known problems with regard to what has come to be known as the "Year 2000 problem." All internal representations of dates within the computational kernel are in the form of high-level expression structures that are capable of representing arbitrary dates.
		Certain aspects of the software make use of the host operating system's real-time clock, for example, in order to learn the current date and time.
		Mathematica is therefore limited by the operating system it is running on, but these limitations are inherent to the operating system, not Mathematica, and correct functioning extends well beyond the year 2000 in all systems for which Mathematica is available.
	www.wolfram.com /news/compliance.html (151 words)

	Year 2000 Problem (Site not responding. Last check: 2007-10-23)
		No where is this impact more profound than in the mariad of intelligent fire detection, suppression and life saving systems that stand guard over our homes, hotels, factories, airports, airplanes, ships, schools and colleges, and entertainment complexes just to name e a few.
		Virtually all of these systems are victims of the Y2K or Year 2000 problem.
		The following pages have been assembled in an effort to help you assess the significance of your individual situation and to help point you to resources who are diligent looking for ways to resolve the problem.
	www.firefire.com /year2000.htm (443 words)

	Open Directory - Computers: Software: Year 2000 (Site not responding. Last check: 2007-10-23)
		Year 2000 - Detailed information on the Y2K from J.R. Stockton.
		Year 2000 Computing Crisis: GAO Reports - Reports from the U.S. General Accounting Office
		Year 2000 Resource Links - Resource links related to software and the year 2000.
	dmoz.org /Computers/Software/Year_2000 (224 words)

	Year 2000 Date Problem - Support Centre (CompInfo)
		This section covers matters to make your computer systems achieve Year 2000 compliance to protect your company or organisation into the next century.
		Year 2000 and EURO: IT challenges of the century
		Year 2000 - Fifty Excuses for not doing anything (Peter de Jager).
	www.compinfo.co.uk /y2k.htm (718 words)

	Year 2000
		This is to remind you that some computer systems and software applications currently used in medical devices, including embedded microprocessors, may experience problems beginning January 1, 2000 due to their use of two-digit fields for date representation.
		Manufacturers need not submit Premarket Approval Application Supplements for Class III devices to document that they have addressed year-2000 problems, provided that the modifications made in the device do not change other aspects of its performance.
		In addition, information concerning medical device regulatory issues may be found on the CDRH home page, at http://www.fda.gov/cdrh.
	www.fda.gov /cdrh/yr2000.html (453 words)

Try your search on: Qwika (all wikis)