1. Year 2000 Computer Bug Hoax year 2000 computer Bug Hoax. The hysteria surrounding the year 2000 computerbug will be the biggest moneymaking hoax in my lifetime. http://www.angelfire.com/oh/justanumber/

var cm_role = "live" var cm_host = "angelfire.lycos.com" var cm_taxid = "/memberembedded" Year 2000 Computer Bug Hoax POSTSCRIPT This website was frozen on December 31, 1999, as a permanent document on how all of us acted and reacted to the Y2K myth from 1997 to 1999. Enjoy reading all of the emails , especially the wild ones from 1998. - David Robert Loblaw, 03 January 2000 A Canadian's opinion piece on this mischievous deception The hysteria surrounding the Year 2000 computer bug will be the biggest money-making hoax in my lifetime. This web-site, originally created in the Fall of '97, is my way of congratulating everyone involved in this elaborate and perfectly-executed scam. Well done! I’m in awe of the people who inflated this issue from a simple computer problem into mythical proportions. I don’t want it stopped; I’m eager to continue to watch the hoax unfold. There is no way it can be stopped anyway as far too many people have an interest in this being perceived as a big problem. No one who’s making money on it or whose reputation is on the line is going to drop their poker face until 01/01/00.

2. CPSR Y2K Working Group The CPSR Y2K Working Group website is filled with upto-date information on the Year 2000 Problem. Contingency planning individual preparedness guidelines. governments, and economies by the year 2000 computer problem, a threat that could disrupt uses this site to promote year 2000 awareness, mitigation, contingency planning, and http://www.cpsr.org/program/y2k

Computer Professionals for Social Responsibility CPSR Y2K Working Group Y2K HOME UPDATES About CPSR FAQ Y2K Policy ... What Is Y2K? Welcome to the CPSR Y2K Working Group Homepage. This web site is provided by CPSR as a public service. CPSR believes that governments and organizations worldwide must immediately address the very serious threat posed to individuals, organizations, governments, and economies by the Year 2000 computer problem, a threat that could disrupt our economic and social systems. We are pleased to announce the CPSR Winter Newsletter devoted to Y2K . It features articles from prominent scientists and fiction from Arthur C. Clarke The Y2K Working Group uses this site to promote year 2000 awareness, mitigation, contingency planning, and preparedness. In particular, we seek to speak and act for the segments of society which do not have extensive resources or organized groups to speak for them. We seek to foster a sense of urgency at all levels local, national and global, while helping the public and the media understand and prepare for the impact of the Y2k problem. Finally, we urge government and business leaders to step up to this challenge and provide leadership, education, and prevention.

3. FHWA - The Year 2000 Computer Problem The roots of the year 2000 computer problem date back to the time when data storage on computers strong action on the year 2000 computer problem in the late 1980s http://www.fhwa.dot.gov/y2k

The Year 2000 Computer Problem FHWA Year 2000 Program ITS Year 2000 Summit U.S. DOT Year 2000 Programs Federal Government Year 2000 Programs ... COTS Database Search Federal Highway Administration and the Year 2000 Computer Problem Y2K Thanks from Secretary Slater and Deputy Secretary Downey 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. The problem now is that years stored as "00" or "01" would be considered to be the years "1900" and "1901" by these older 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. The Federal Highway Administration (FHWA) began taking a strong action on the Year 2000 computer problem in the late 1980s. At that time, FHWA designed the Agency's flagship information system, the Fiscal Management Information System (FMIS), with 4-digit date fields. In September 1997, the FHWA was recognized by Representative Steve Horn, Chair of the House Government Oversight and Reform Committee's Information Technology Panel as being one of two Federal agencies (the other was the Social Security Administration) that began Year 2000 repair work well before anyone in Congress knew there was a problem. Since then, FHWA has made great strides towards making all FHWA information systems and technology Year 2000 compliant.

4. Iin120 - Year 2000 Computer Problem Subject year 2000 computer Problem. As part of the National Science Foundation's (NSF) activities related to potential problems associated with Year 2000, NSF wishes to remind its http://www.nsf.gov/pubs/1997/iin120/iin120.htm

NATIONAL SCIENCE FOUNDATION Office of the Director ARLINGTON, VIRGINIA 22230 Notice No. 120 June 27, 1997 IMPORTANT NOTICE TO PRESIDENTS OF UNIVERSITIES AND COLLEGES AND HEADS OF OTHER NATIONAL SCIENCE FOUNDATION GRANTEE ORGANIZATIONS Subject: Year 2000 Computer Problem As part of the National Science Foundation's (NSF) activities related to potential problems associated with Year 2000, NSF wishes to remind its awardees of their responsibilities under NSF grants and cooperative agreements. Recipients of NSF grants and cooperative agreements generally have full responsibility for the scientific, administrative, and financial aspects of the activity being supported. This responsibility extends to anticipating and reacting to events such as the Year 2000 and taking all steps necessary to mitigate potential problems that might be caused by the Year 2000. Many computer systems may experience operational difficulties because they are unable to handle the change from the year 1999 to the year 2000. Others may fail because they do not properly consider 2000 a leap year. For computer systems that use two digits to represent the year, calculations, comparisons, and data sorting my be adversely affected. This would include computer systems ranging from the desktop to the largest mainframe. Awardees should also be aware that the Year 2000 may affect electronic devices utilizing embedded microchips that perform date-based calculations. Biomedical devices and other laboratory equipment may depend upon embedded date functions. If the chip receives what it perceives to be an invalid date, it may fail, impacting important experiments. False date comparisons may invalidate test results, leading to false conclusions.

5. Everything 2000 - Computer Obviously, the global glitch known as the Y2K Computer Crisis has come and gone without any major burps Time Bomb 2000 What the year 2000 computer Crisis Means to http://www.everything2000.com/computer/a_computer.asp

Obviously, the global glitch known as the Y2K Computer Crisis has come and gone without any major burps to speak of. Still, there is interest in what happened and why. This section contains those stories as well as links to promient companies that were involved in the fixes. Y2K News Y2K "Leaps" Pass Final Hurdle Leap Year computer problems are few leaving bug nearly exterminated Full story Y2K Money Well Spent Experts say the $100 Billion spent on the computer bug was necessary Full story... Y2K Drug Stockpiling Prevented No increase in prescriptions during end of year Full story.. Y2K Over, What's Next? Those who spent years working on Y2K computer fixes begin looking for next job Full story... Y2K Panic Cash Collected Bank vaults full of extra money emptied and sent back to Federal Reserve Full story...

6. Y2K Clearing House Welcome to the National Year 2000 (Y2K) Clearinghouse. This website is a combination of the clearinghouse for information on the year 2000 computer problem. It is maintained http://www.y2k.gov/

Home General Information Lessons learned Press Release Archive ... Sector Pages W elcome to the National Year 2000 (Y2K) Clearinghouse. This website is a combination of the President's Council on Year 2000 Conversion, the Chief Information Officer's Council Committee on Year 2000, and the U.S. Federal Gateway for Year 2000 Information Directories. T his clearinghouse creates a single repository of Y2K information to assist the public, business, academia, Federal, state and local governments in obtaining various Y2K information. T he National Y2K Clearinghouse web site is in the process of being finalized. Please send an e-mail message to Mike Johnson at mike.johnson@gsa.gov regarding any departmental information (in particular Y2K lessons learned) you would like to have included in the National Y2K Clearinghouse web site. To those of you that have provided content for the National Y2K Clearinghouse web site, thank you. F or a list of instructions on how to submit your Y2K information please press here This web site is a clearinghouse for information on the Year 2000 computer problem. It is maintained by the

7. Year 2000 Computer Bug Hoax: A Simple Explanation year 2000 computer Bug Hoax A Simple Explanation. POSTSCRIPT Thiswebsite was frozen on December 31, 1999, as a permanent document http://www.angelfire.com/oh/justanumber/whatitis.html

var cm_role = "live" var cm_host = "angelfire.lycos.com" var cm_taxid = "/memberembedded" Year 2000 Computer Bug Hoax: A Simple Explanation POSTSCRIPT This website was frozen on December 31, 1999, as a permanent document on how all of us acted and reacted to the Y2K myth from 1997 to 1999. There will be no updates. Enjoy reading all of the emails , especially the wild ones from 1998. - David Robert Loblaw, 03 January 2000 Millennium Bug is a misnomer Millennium ... The Year 2000 is not the start of the next millennium . Even if it was, this date-field issue has nothing to do with thousand year cycles. If computers existed in 1899, we'd have called it The Year 1900 Problem. ... Bug A bug is an unforeseen blip in software and other development. Microsnot is the world leader in this. The Year 2000 issue is just that an issue, not a bug. What it is Decades ago, well-dressed computer programmers collectively and individually decided not to include the unnecessary "19" century digits before every year date. By doing so, this saved a lot of valuable, expensive, and rare memory space (back then). It was a responsible and logical decision. If they did not do this, our current computer technology would probably be hovering around the early 1980's mark. People today would be drooling over possibly owning a

8. Year 2000 AZ Index Feedback. year 2000 computer Problem. June 25, 1997 hazard and safety analyses to determine whether device performance could be affected by the year-2000 date change http://www.fda.gov/cdrh/yr2000.html

CDRH Home Search A-Z Index Feedback Year 2000 Computer Problem June 25, 1997 Dear Medical Device Manufacturer: 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. In addition to adversely affecting the functioning of some devices, the two-digit date format could also affect computer-controlled design, production or quality control processes. To ensure the continued safety and effectiveness of these devices, we are recommending the following actions: For future medical device premarket submissions, manufacturers should assure that the products can perform date recording and computations that will be unaffected by the year-2000 date change. For currently manufactured medical devices, manufacturers should conduct hazard and safety analyses to determine whether device performance could be affected by the year-2000 date change. If these analyses show that device safety or effectiveness could be affected, then appropriate steps should be taken to correct current production and to assist customers who have purchased such devices. For computer-controlled design, production and quality control processes

9. Y2K For Women The Year 2000 Computer Problem What Every Woman What s the Big Deal About Y2K? The year 2000 computer Problem What EveryWoman Needs to Know and How to Keep Herself and Her Family Safe. http://www.y2kwomen.com/keeper/

10. Oreilly.com -- Online Catalog: Year 2000 In A Nutshell Book by Norman Shakespeare. Addresses the year 2000 computer dilemma, providing a compact compendium of solutions and reference information useful for addressing the problem. Includes a comprehensive COBOL quick reference, plus reference for daterelated functions. http://www.oreilly.com/catalog/y2knut/

O'Reilly Home Press Room Jobs Resource Centers Perl Java Python C/C++ ... Enterprise Development Book Series Hacks Head First Cookbooks In a Nutshell ... Developer's Notebooks Publishing Partners No Starch Press Paraglyph Press Pragmatic Bookshelf Syngress Publishing Online Publications LinuxDevCenter.com MacDevCenter.com WindowsDevCenter.com ONDotnet.com ... XML.com Special Interest Events Meerkat News Ask Tim tim.oreilly.com ... Open Books Special Sales Academic Corporate Government Inside O'Reilly About O'Reilly International Advertise with Us Contact Us ... Bookstores Traveling to a tech show? Hotel Search Hotel Discounts Discount Hotels Chicago Hotels ... Register your book to get email notification of new editions, special offers, and more. Year 2000 in a Nutshell By  Norman Shakespeare September 1998 Series: In a Nutshell ISBN: 1-56592-421-5 This book is out of print. Buy from O'Reilly: This reference guide addresses the awareness, the managerial aspect, and the technical issues of the Year 2000 computer dilemma, providing a compact compendium of solutions and reference information useful for addressing the problem. Includes a comprehensive Cobol quick reference, plus reference for date-related functions in many other languages. Also includes templates, worksheets, and action plans. [ Full Description O'Reilly Newsletters Stay informed.

11. Year 2000 year 2000 computer Problem. June 25, 1997. Dear Medical Device ManufacturerThis is to remind you that some computer systems and http://www.fda.gov/cdrh/yr2000/cdrh/letters/970625/yr2000.html

Year 2000 Computer Problem June 25, 1997 Dear Medical Device Manufacturer: 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. In addition to adversely affecting the functioning of some devices, the two-digit date format could also affect computer-controlled design, production or quality control processes. To ensure the continued safety and effectiveness of these devices, we are recommending the following actions: For future medical device premarket submissions, manufacturers should assure that the products can perform date recording and computations that will be unaffected by the year-2000 date change. For currently manufactured medical devices, manufacturers should conduct hazard and safety analyses to determine whether device performance could be affected by the year-2000 date change. If these analyses show that device safety or effectiveness could be affected, then appropriate steps should be taken to correct current production and to assist customers who have purchased such devices. For computer-controlled design, production and quality control processes

12. Reptilian Associates Survival/Disaster Preparation (former Y2K Page) An introduction to year 2000 computer problems and what they will mean to you. How to protect yourself from year 2000 problems. Plus references and links. http://www.ecis.com/~alizard/y2k.html

Reptilian Associates Survival/Disaster Preparation (former Y2K page) ©1998,©1999,©2000,©2001,©2002,©2003 by Reptilian Associates. Reproduction of this or any document on this site (http://www.ecis.com/~alizard) for non-commercial use is permitted as long as this notice is included and a pointer to this site is included. To reproduce this document for commercial or governmental distribution, whether for print or a for-profit Web site, request permission from image use by permission of Namebase new page counter when I get around to it The probability of massive Y2K trouble is safely passed. The worst problem I had was a massive hangover. This page in its original form has served its purpose. I'm retaining the page content here which appears to me to have use for the future. Content solely relating to Y2K has or will be deleted sooner or later. This page is going to have a chopped-up look for a while. [several months later] The page still needs more revision, sorry I haven't had time yet. However, if you want to protect yourself against the latest round of terrorist threats, this should be a good starting point. If biowar gets serious, having a few weeks of food stashed in the pantry so you don't have to worry about meeting your infected fellow citizens at the grocery store might be a good idea. [written in Feb 2003] As I write this, anti-aircraft guns are in the streets of Washington, DC , the nation's "terrorist alert" status is either orange or red, and FEMA is telling people to go forth and buy duct tape and plastic sheeting to defend against biological and chemical agents. You may find information on disaster prep that's a bit more useful here.

13. NSF: Year 2000 Information - MYTHS AND FACTS Many common beliefs about the year 2000 computer problemalso known as themillennium bug or simply Y2K are marked by simplistic assumptions. http://www.nsf.gov/oirm/y2k/myths.htm

YEAR 2000 MYTHS AND FACTS The following piece concerns the general year 2000 problem, that is, not just as it pertains to a university researcher but as it pertains to a large industry or government agency as well. We include it here to provide you with a wider understanding of the overall problem in the hope that this will be helpful when you examine the systems that support your particular funded activities. Many common beliefs about the Year 2000 computer problemalso known as "the millennium bug" or simply "Y2K"are marked by simplistic assumptions. To effectively address this problem, it must first be better understood. Below are brief statements of some common Y2K myths and their corresponding facts. For additional explanation of any of these pairs, select the MORE link. Myth: Y2K is easy to understand and straightforward to fix. Fact: Y2K is hard to understand and difficult to fix. MORE Myth: The Y2K problem is an event that occurs at midnight on December 31, 1999. Fact: The Y2K problem has already begun and will exist long after January 1, 2000. MORE Myth: Y2K is primarily about how systems are designed.

14. DefenseLINK: Defense Policy On The Year 2000 Computer Conversion Issue US Department of Defense Header Image (click to return to US Department of Defensehomepage). Updated 20 Aug 1999. Year 2000 (Y2K) Computer Conversion Issue. http://www.defenselink.mil/issues/y2k.html

Jun. 12, 2004 War on Terror Transformation News Products Press Resources ... Contact Us Updated: 20 Aug 1999 Year 2000 (Y2K) Computer Conversion Issue "The millennium bug is a vivid and powerful reminder of the ways that we are growing ever more independent as we rise to the challenges of this new era. When our founding fathers urged us to form a more perfect union, I don't think they had this in mind, but they might be quite pleased. The powerful forces of change that have created unimagined abundance also bear within them, as is consistent with human nature, the possibilities of new and unexpected challenges. But if we act properly, we won't look back on this as a headache, sort of the last failed challenge of the 20 th century. It will be the first challenge of the 21st century successfully met. That is the American way, and together we can do it." President Clinton July 14, 1998 RELATED PUBLICATIONS RELATED SITES RELATED NEWS ARTICLES (Launch a 60 second search) RELATED NEWS RELEASES/TRANSCRIPTS (Launch a 60 second search) Related Publications DoD Year 2000 Management Plan Checklist from the DLA Systems Design Center Defense Data Dictionary System - DoD Data Standards: Direct link to DoD Data Administration Home Page (Look here for guidance on data element standards for dates) Crosstalk, the Journal of Defense Software Engineering

15. NIH Guide: NOTICE REGARDING THE YEAR 2000 COMPUTER PROBLEM NOTICE REGARDING THE year 2000 computer PROBLEM Release Date April 3, 1998 PT NationalInstitutes of Health As part of the National Institutes of Health s (NIH http://grants.nih.gov/grants/guide/notice-files/not98-046.html

http://www.nih.gov/grants/oer.htm . Information pertaining to the NIH-wide Year 2000 activities can be found at NIH's Office of Information Resource Management's (OIRM) web site at http://wwwoirm.nih.gov/y2000/. This site includes a link to FIPS PUB 4-1. Information concerning interagency Year 2000 activities, plans, and issues can be found on the General Services Administration's web site at http://www.itpolicy.gsa.gov under the Year 2000 Information Directory. Return to Volume Index Return to NIH Guide Main Index Department of Health and Human Services National Institutes of Health (NIH) 9000 Rockville Pike Bethesda, Maryland 20892

16. Year 2000 Computer Preparedness - Yale-New Haven Hospital year 2000 computer Preparedness. Because Year 2000 has the potentialto disrupt the normal operation of computer systems, YaleNew http://www.ynhh.org/general/year_2000.html

17. Year 2000 Computer Problem Spring 1998 Technical Update General Interest. year 2000 computer Problem.In a nutshell, the year 2000 computer Problem is that during http://www.uc.edu/ucitnow/spring_98/prob.html

Spring 1998 Technical Update General Interest Year 2000 Computer Problem In a nutshell, the Year 2000 Computer Problem is that during the 1960s, '70s and '80s, most programs were written using the date format MM/DD/YY and the programs assume that the first two digits of any given year are "19." Computers running such programs require attention to be able to distinguish between centuries. Left untreated, come New Year's Day, 1 January 2000, computers all over the globe could be producing errors, horrifying users with application failures - and crashing. On the surface, this seems like a small problem. But finding the appropriate lines of code - particularly in programs for which the source code may no longer be available! - makes looking for a needle in a haystack child's play by comparison. Finding, fixing and testing date-related processes in computer systems will require significant resources at the University of Cincinnati and throughout the world. For more information, please visit the

18. The Year 2000 Computer Problems Testimony on The year 2000 computer Problems by John Callahan Assistant Secretaryfor Management and Budget and Chief Information Officer US Department of http://www.hhs.gov/asl/testify/t980507a.html

This is an archive page. The links are no longer being updated. Testimony on The Year 2000 Computer Problems by John Callahan Assistant Secretary for Management and Budget and Chief Information Officer U.S. Department of Health and Human Services Before the House Committee on Ways and Means, Subcommittee on Oversight May 7, 1998 Good morning. I am John Callahan, Assistant Secretary of the Department of Health and Human Services for Management and Budget (ASMB) and Chief Information Officer (CIO). I am pleased to appear before this Subcommittee to provide you with a report on the accomplishments of the Department and the challenges faced by the Department in assuring that our systems are Millennium compliant. We will especially emphasize the Year 2000 progress made by HCFA and ACF. I am accompanied today by Gary Christoph, CIO of the Health Care Financing Administration (HCFA), and by Elizabeth James, CIO of the Administration for Children and Families (ACF), and Norm Thompson, Associate Commissioner for Automation and Special Projects in ACF's Office of Child Support Enforcement. HHS' YEAR 2000 EFFORT The Secretary, the Deputy Secretary, and I have declared the Year 2000 (Y2K) date issue to be our highest information technology priority. We have already taken several steps, and we will continue to take action, to ensure that all HHS information systems are Year 2000 compliant. We have involved all parts of our organization, including staff with expertise in information systems, budget, human resources, and acquisition management in solving the Year 2000 problem. No matter what else we do and what other initiatives we undertake, we must ensure that our ability to accomplish the Department's mission is not impaired.

19. The Year 2000 Computer Problems Testimony on The year 2000 computer Problems by John Callahan Assistant Secretaryfor Management and Budget And Chief Information Officer US Department of http://www.hhs.gov/asl/testify/t980610a.html

This is an archive page. The links are no longer being updated. Testimony on The Year 2000 Computer Problems by John Callahan Assistant Secretary for Management and Budget And Chief Information Officer U.S. Department of Health and Human Services Before the House Committee on Government Reform and Oversight, Subcommittee on Government Management, Information and Technology June 10, 1998 INTRODUCTION Good morning. I am John Callahan, Assistant Secretary of the Department of Health and Human Services for Management and Budget (ASMB) and Chief Information Officer (CIO). I am pleased to appear before this Subcommittee to provide you with a report on the accomplishments and the challenges faced by the U.S. Department of Health and Human Services (HHS) in assuring that our systems are Millennium compliant. The Secretary, the Deputy Secretary, and I have declared the Year 2000 date issue to be our highest information technology priority. We have taken and will continue to take actions to ensure that HHS information systems are Year 2000 compliant. We have involved all parts of our organization, including staff with expertise in information systems, budget, human resources, and acquisition management in solving the Year 2000 problem. No matter what else we do and what other initiatives we undertake, we must ensure that our ability to accomplish the Department's mission is not impaired.

20. Year 2000 Research Center The year 2000 computer Problem Gary Beach, CIO Magazine s publisher, testifiedbefore congress on the fallout from Y2K and its effect on the future of IT. http://www.cio.com/research/y2k/

IN THIS RESEARCH CENTER Front Page CIO Articles Other Articles Resources ... CIO This Research Center provides links to relevant Web sites, articles and white papers, and a virtual roundtable with industry experts and CIO editors about the Y2K "crisis". The Year 2000 Computer Problem Gary Beach, CIO Magazine's publisher, testified before congress on the fallout from Y2K and its effect on the future of IT. January 27, 2000 - Prepared Testimony Y2K Experts Poll Who’s ready, who’s not? Conducted by an informal public-interest coalition of CIO Magazine, ISACA, and Dr. Ed Yardeni's Y2K Center. Sound Off Asks:  How Much Will the Y2K Act Cost You?  The Y2K Act limits legal liability for Year 2000 computer problems. Does this let irresponsible software vendors off the hook? Give your opinion CIO Connection Discussion Forum Discussion on topics such as Y2K event staffing issues CIO Radio Talks to  Dick Lefkon Editor of the book Year 2000: Best Practices for Year 2000 Millenium Computing (Part One) Dick Lefkon (Part Two) and Stephen Roach CIO Articles Reports on the challenges—and imperatives—of making information systems year 2000 compliant.

A  B  C  D  E  F  G  H  I  J  K  L  M  N  O  P  Q  R  S  T  U  V  W  X  Y  Z

Page 1     1-20 of 99    1  | 2  | 3  | 4  | 5  | Next 20