Geometry.Net - Basic_Y: Year 2000 Computer


Home - Basic_Y - Year 2000 Computer

e99.com Bookstore

Images

Newsgroups

21-40 of 104 Back | 1 | 2 | 3 | 4 | 5 | 6 | Next 20

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

Year 2000 Computer: more books (100)

Y2K: ready, set, test.(Mortgage Bankers Assn. of America's guidelines on addressing the year 2000 computer problem): An article from: Mortgage Banking
Clock ticking on Y2K liabilities.(potential Year 2000 computer glitches): An article from: National Underwriter Property & Casualty-Risk & Benefits Management by Lee Ann Gjertsen, 1997-12-01
Got Beans?; Get Ready for the Year 2000 Computer Crisis by Ingrid Harding, 1998-11-15
Mission impossible? The state's Y2K plan.(Alaska's initiatives for the year 2000 computer problem): An article from: Alaska Business Monthly by Saundra Middleton, 1998-12-01
A vision of computer-aided casting in the year 2000. (Computers in the Foundry): An article from: Modern Casting by Constantine D. Orogo, Hubert D. Callihan, et all 1993-10-01
How to Survive and Prosper After the 'Year 2000' Computer CRASH by David, M. Price, 1998-06-06
Early this year.(year 2000 computer transition and the publication of "Notes")(Brief Article): An article from: Notes
Y2K snarls could show up on state and local audits.(year 2000 computer crisis): An article from: State Legislatures
Summer off to slow start.(coverage of the Americans with Disabilities Act; Year 2000 computer liability bill): An article from: Do-It-Yourself Retailing
Lie-2K : Why the Alleged End-of-the-World Year-2000 Computer Crisis is Really Just a Hoax by Sherman S. Smith, 1999-07-01
Year 2000 computer problem: Hearing before the Committee on Agriculture, Nutrition, and Forestry, United States Senate, One Hundred Fifth Congress, second session ... July 22, 1998 (S. hrg) by United States, 1999
Millennium Bug! Protecting Yourself from the Year 2000 Computer Crisis by William Trench, 1998-11-01
Transporting Alaska into the new millennium.(Alaska's transportation industry addresses year 2000 computer problem): An article from: Alaska Business Monthly by Saundra Middleton, 1999-04-01
The year 2000 computer problem: Will the health care industry be ready? : hearing before the Special Committee on the Year 2000 Technology Problem, United ... deadlines, July 23, 1998 (S. hrg) by United States, 1998

lists with details

NRC: SECY-99-134 - Agency Contingency Plans For The Year 2000 Computer Problem I
SUBJECT, AGENCY CONTINGENCY PLANS FOR THE year 2000 computer PROBLEM IN THE These systems may misread the year 2000 and cause the systems to fail,
http://www.nrc.gov/reading-rm/doc-collections/commission/secys/1999/secy1999-134

Extractions: Executive Director for Operations SUBJECT: AGENCY CONTINGENCY PLANS FOR THE YEAR 2000 COMPUTER PROBLEM IN THE NUCLEAR INDUSTRY PURPOSE: To obtain Commission approval of agency contingency plans dealing with the Year 2000 (Y2K) problem in the nuclear industry. BACKGROUND: The Y2K problem pertains to the potential inability of computers to correctly recognize dates and results primarily from computer hardware or software that uses two-digit fields to represent the year. These systems may misread the year 2000 and cause the systems to fail, generate faulty data, or act in an incorrect manner. The Y2K problem has the potential to interfere with the proper operation of any computer system (including embedded systems), software, or database. The staff is pursuing a comprehensive program for dealing with potential Y2K problems. The staff completed Y2K remediation of its own systems on February 5, 1999, ahead of the OMB target of March 31, 1999. Because of the nature of the Y2K problem, the staff has prepared contingency/business continuity plans for its mission-critical systems, specifically addressing failures that have the potential to result from the Y2K problem. Additionally, the staff has been working with nuclear industry organizations and licensees since 1996 to address the Y2K problem. On the basis of audits and inspections of nuclear power plant, fuel cycle facility, and materials licensee Y2K programs to date, we are confident that our licensees will be Y2K ready by December 31, 1999, and that the Y2K transition will not affect the continued safe operation of our licensed facilities.
GAO: Year 2000 Computing Crisis: GAO Reports, Etc.
Defense Computers US Space Command s Management of Its Year 2000 Defense Computers year 2000 computer Problems Put Navy Operations at Risk.
http://www.gao.gov/y2kr.htm

Extractions: Free readers for PDF files and more information about PDF are available from Adobe Systems, Inc. Follow this link for tips on how to use the Acrobat Reader. For additional information visit the GAO Home Page Year 2000 Computing Crisis: Business Continuity and Contingency Planning GAO/AIMD-10.1.19 . August 1998. [Available in PDF version only] Y2K Computing Challenge: Day One Planning and Operations Guide GAO/AIMD-10.1.22 [Available in PDF version only] (Reports and Testimonies are listed in reverse date order, newest first.) Defense Computers: U.S. Space Command's Management of Its Year 2000 Operational Testing.
The Year 2000 Computer Problem
The year 2000 computer Problem Issues for Small Jurisdictions Test your computers, including servers, for Year 2000 compatibility.
http://www.mrsc.org/focuspub/yk2foc.aspx

Extractions: document.write("") document.write("") document.write("") document.write("") document.write("") document.write("") document.write("") Legal Resources Research Tools Subjects Services ... Sample Local Government Docs document.write("") MRSC Research Briefs Printer Friendly First of all, what is the Year 2000 problem? To conserve storage space in the early days of computing, years were stored as two digits rather than as four (for example, 98 rather than 1998) in computer programs. If your software programs are not updated to handle four digits, then calculations involving dates could be incorrect, affecting a variety of your financial and database systems. A sEcond problem with the Year 2000 will occur because the clocks in many personal computers store years as two digits and have no place holder for the millennium value of a year, requiring that you update your hardware. Further, the Year 2000 is a leap year, but the rules governing computing dates will fail to recognize 2000 as a leap year. What does the Year 2000 problem mean for small cities, towns, and counties within Washington State?
NIH Guide: NOTICE REGARDING THE YEAR 2000 COMPUTER PROBLEM
NOTICE REGARDING THE year 2000 computer PROBLEM Release Date April 3, 1998 PT National Institutes of Health As part of the National Institutes of Health s
http://grants.nih.gov/grants/guide/notice-files/not98-046.html

Extractions: 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
FindLaw For Legal Professionals - Case Law, Federal And State Resources, Forms,
FindLaw for Legal Professionals is a free resource for attorneys that includes online case law, free state codes, free federal codes, free legal forms,
http://caselaw.lp.findlaw.com/casecode/uscodes/15/chapters/92/toc.html

Extractions: //For Jeff's Modules. var what="LNCAI"; var uri=document.location; FindLaw For the Public For Small Business For Corporate Counsel ... Supreme Court Cases My current location: city Change Location Title 15 U.S. Code Document Library Legal Dictionary Legal News FindLaw Guide LawCrawler Web US Gov Sites Mailing List Archives Sup Court 1893+ US Fed Circuits US Constitution United States Code TITLE 15 - COMMERCE AND TRADE CHAPTER 92 - YEAR 2000 COMPUTER DATE CHANGE Section 6601. Findings And Purposes Section 6602. Definitions Section 6603. Application Of Chapter Section 6604. Punitive Damages Limitations Section 6605. Proportionate Liability Section 6606. Prelitigation Notice Section 6607. Pleading Requirements Section 6608. Duty To Mitigate Section 6609. Application Of Existing Impossibility Or Commercial Impracticability Doctrines Section 6610. Damages Limitation By Contract Section 6611. Damages In Tort Claims Section 6612. State Of Mind; Bystander Liability; Control Section 6613.
Y2K For Women -- The Year 2000 Computer Problem: What Every Woman Needs To Know
Y2K for Women What every woman needs to know about the Year 2000 Problem and how to keep herself and her family safe.
http://www.scorpioncity.com/y2kwomen.html

Extractions: Y2K for Women Home Welcome to Y2K Women the Year 2000 Problem Site Exclusively Designed for Women Many people (men and women alike) don't know how to handle an overwhelming problem like Y2K a situation that's riddled with change and anxiety. So they, in essence, "shut down" and don't even want to think about it , let alone make any plans!
Y2K For Conmen -- The Year 2000 Computer Problem: What Every Conman/Conwoman Nee
The year 2000 computer Problem What Every Conman Needs to Know and Welcome to Y2K Conmen the Year 2000 Problem Site Exclusively Designed for Conmen
http://www.scorpioncity.com/y2kconmen.html

Extractions: What's New Back Issues Sign the GuestBook Introduction: How I Found Out About Y2K ... Y2K News Magazine Chat Room for Y2K Conmen - Talk with others and exchange ideas 24 hours a day! In cooperation with Y2K News Magazine. Y2K for Conmen has been mentioned in several publications and articles in The Press Room Y2K for Conmen Home Welcome to Y2K Conmen the Year 2000 Problem Site Exclusively Designed for Conmen and other ripoff artists Many people (men and women alike) don't know how to handle an overwhelming problem like Y2K a situation that's riddled with change and anxiety. So they, in essence, "shut down" and don't even want to think about it , let alone make any plans! You can take advantage of these people! This book will show you how. Y2K For Conmen is designed to explain the Year 2000 Problem (Y2K) to conmen who have no, or very limited, computer knowledge, but still want to make money from it.
Date With Destiny: The Year 2000 Computer Bug (Research Note 35 1997-98)
The Y2K problem comes with the Year 2000 when computers may instead think it is 1900. Banks might then calculate account interest over 100 years!
http://www.aph.gov.au/library/pubs/rn/1997-98/98rn35.htm

Extractions: 23 March 1998 Millennium Scaremongering There are predictions of gloom and doom for the arrival of the centesimal year in 2000 relating to modern computer systems. These may not act as usual when the first day of Year 2000 arrives. Prudence may be wise for certain crucial sectors such as airlines. Qantas and Ansett may spend $150 million working on fixes. Aircraft might not fly on the night in question. Pacemaker wearers may be wise to stay at a hospital overnight. Stockmarkets may best remain closed for the duration. Computer systems of various forms exist within cars, hospitals, aircraft, offices, communications networks, financial institutions, missiles, shops and in almost any other sphere of modern business and technology. They need the correct date to work properly or they may cause system failures. It is the embedded code within the microchips and computer circuits where the devil lies with the Year 2000 (Y2K) computer bug. In the early days of computers, it was necessary to limit the amount of input data as much as possible, in order to maximise processing storage. As a consequence, when inputting years, the prefix '19' was often left out. The Y2K problem comes with the Year 2000 when computers may instead think it is 1900. Banks might then calculate account interest over 100 years!
Government Provides Tax Relief To Small Businesses For Year 2000 Computer Compli
The year 2000 computer problem presents a serious economic challenge for the Additional Allowance year 2000 computer Hardware and Systems Software
http://www.fin.gc.ca/news98/98-057e.html

Extractions: Annual lists Ottawa, June 11, 1998 Related documents: Finance Minister Paul Martin today announced tax relief for small- and medium-sized businesses to address the year 2000 computer compliance problem. This announcement falls within the wider context of the government's role in responding to the year 2000 challenge, which is being jointly co-ordinated by Industry Minister John Manley and Treasury Board President Marcel Massé. Under the tax relief announced today, accelerated capital cost allowance (CCA) deductions of up to $50,000 will be provided to small- and medium-sized firms for computer hardware and software acquired to replace systems that are not year 2000 compliant. This will allow smaller firms to deduct 100 per cent of eligible expenditures in the year in which they occur. Although many firms have taken action to ensure that their computer systems will be ready for the year 2000, a large number still have not addressed this issue.
The Year 2000 Computer Problem
the leap from the year 1999 to 2000 will in computers´minds- rather be a jump from 99 to http//www.year2000.com/ Year 2000 Information Center
http://www.klinik.uni-frankfurt.de/surgery-online/y2k.htm

Extractions: whereas '00' until today is defined as ' Any software that use dates (practically any do) internally, for instance to store dates - when files where stored, modified or created - ,will cope with the virtual 'jump backward' only, as long as there are no calculations performed, that deal with differences of dates are not predictable either on singular workstations or computers "on the Net", as time is known to proceed forward only ( Albert EINSTEIN Thinking about a 'banking software' that works in any country of the world, using the two-digit-code, this one might be the cause of a major breakdown of the net connected to.
Frequently Asked Questions About The Year 2000 Computer Problem
What is the Year 2000 (Y2K) computer problem? A number of computer programs represented the date of a year by using two digits. In these programs, the year
http://www.socp.org/majorinitiatives/cyberth1.html

Extractions: The International Y2K Workshop was sponsored by the Y2k Information Coordination Center (ICC) , and was led by the CERT® Coordination Center (CERT/CC) This "Frequently Asked Questions" document is intended to be a "living" document, and new questions and additional information will be added to it as we receive them. Please check back regularly for updates. Updated: November 24, 1999 (added info from the International Y2K Workshop, Y2K Failure vs. Attack FAQ Working Group)
The Year 2000 Computer Problems
Testimony on The year 2000 computer Problems by John Callahan Assistant Secretary for Management and Budget And Chief Information Officer
http://www.hhs.gov/asl/testify/t980610a.html

Extractions: 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.
The Year 2000 Computer Problems
Testimony on The year 2000 computer Problems by John Callahan Assistant Secretary for Management and Budget and Chief Information Officer
http://www.hhs.gov/asl/testify/t980507a.html

Extractions: 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.
Year 2000 Computer Bug Demands Attention Today
And it s bringing with it the year 2000 computer bug, a glitch in computer programs at Harvard University and around the world caused by programmers noting
http://www.news.harvard.edu/gazette/1997/11.13/Year2000Compute.html
Harvard Seeks To Swat Year 2000 Computer Bug
Harvard Seeks to Swat year 2000 computer Bug. By Alvin Powell. Contributing Writer. The year 2000 is coming and Harvard s computer specialists are preparing
http://www.news.harvard.edu/gazette/1998/05.07/HarvardSeekstoS.html

Extractions: SEARCH THE GAZETTE By Alvin Powell Contributing Writer The year 2000 is coming and Harvard's computer specialists are preparing to meet it. The preparation is needed because, along with the new millennium comes the "millennium bug," a worldwide glitch in computer software caused by programmers saving space by noting dates with just two digits. That means that computers, which take everything literally, will assume the year "00" is 1900. If untreated, this seemingly innocuous problem could cause trouble ranging from fax machines marking documents with the date Jan. 1, 1900, to wide-scale disruption of financial networks and power grids. Exactly how large the problem will be is subject to debate. Some doomsayers predict a wave of bankruptcies and a global recession. Others say it will be noticed hardly at all. Most agree, though, that it is a problem worth paying attention to and that early assessment and action can minimize the potential impact. Harvard has been working for more than a year to minimize any disruption. The University has surveyed its many schools and departments, quizzed vendors on their software's "Year 2000 compliance," contacted outside institutions with which it exchanges information electronically, and put a University-wide structure in place with the goal of gaining near-total compliance by January 1999.
Year 2000 Computer Problem
In a nutshell, the year 2000 computer Problem is that during the 1960s, 70s Left untreated, come New Year s Day, 1 January 2000, computers all over the
http://www.uc.edu/ucitnow/winter_98/2000.html

Extractions: Mainframe News 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. Further, 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 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. Return to the Table of Contents
Review Of State's Efforts To Meet Year 2000 Computer Change
The Little Hoover Commission believes that the year 2000 computer problem poses a unique and substantial threat to the State s business operations.
http://www.lhc.ca.gov/lhcdir/y2k.html

Extractions: The Little Hoover Commission believes that the Year 2000 computer problem poses a unique and substantial threat to the State's business operations. And while substantial progress has been made, the Commission believes the efforts to modernize the State's computer systems would benefit from more detailed oversight and creative support on the part of California's top policy makers. Considerable progress has been made by information technology staff in individual departments. The Department of Information Technology (DOIT) through its Year 2000 Program has provided valuable assistance to the project managers assigned the task of modernizing the computers. And most recently some lawmakers have demonstrated the ability of public scrutiny to reinvigorate public agencies charged with resolving high-priority problems. In particular, some legislative budget subcommittees have scrutinized the Year 2000 efforts of individual departments, and some policy committees have provided valuable oversight, including the Senate Select Committee on Procurement, Expenditures and Information Technology; the Senate Select Committee on Economic Development; and the Assembly Information Technology Committee.
Untitled Document
UW advances on year 2000 computer plan. Faculty Lecture nominees sought The year 2000 issue results from the past computer programming practice of
http://depts.washington.edu/uweek/archives/1998.03.MAR_05/_article3.html

Extractions: International TAs studied, policy changes made 102 nominated for staff awards UW advances on year 2000 computer plan Faculty Lecture nominees sought Nanotechnology Center brings Chu and Frankel to campus When men batter women: New insights from UW professors Huckabay fellows will demonstrate projects Thursday UW advances on year 2000 computer plan "Substantial progress" has been made in complying with four recommendations concerning the University's plan to make its computer systems year 2000 compatible, the UW internal auditor told the Board of Regents at its February meeting. The recommendations were outlined in a December 1997 report by the UW Internal Audit Department, which had reviewed the University's overall plan. The progress made on those recommendations is "keeping the University year 2000 project on track," said G. Max Whisler, UW director of audits. http://www.washington.edu/tech_home/2000/ . The site has various links designed to save people research work and to provide basic tools to deal with the situation, Whisler said. The year 2000 issue results from the past computer programming practice of storing the year field as two digits instead of four. If the problem is left uncorrected, hardware devices, system and application software, and other devices controlled by embedded computer chips could shutdown or provide inaccurate information.
SOFT/TIAFT 98 - Y2K: The Year 2000 Computer Bug, Concerns Of A Coroner's Office
Y2K THE year 2000 computer BUG, CONCERNS OF A CORONER S OFFICE AND TOXICOLOGY LABORATORY. Eric S. Lavins, Ronald L. Cechner and Amanda J. Jenkins
http://www.tiaft.org/tiaft98/fri/p/f_p_21.html

Extractions: SOFT TIAFT Poster Session 4 Friday October 9, 1998 Y2K: THE YEAR 2000 COMPUTER BUG, CONCERNS OF A CORONER'S OFFICE AND TOXICOLOGY LABORATORY Eric S. Lavins , Ronald L. Cechner and Amanda J. Jenkins Cuyahoga County Coroner's Office, 2121 Adelbert Road, Cleveland, OH 44106 U.S.A. Y2K is a two-fold problem encompassing both hardware and software. Remedies involve replacing out-of-date software applications and/or upgrading hardware. Data management software as well as PC-interfaced instrumentation (GC, MS, LC, UV/Vis, auto-analyzers etc.) are of concern. "In-house" software poses the most serious problem because the user is unlikely to have the staff or money to expend on major software overhauls. At the Cuyahoga County Coroner's Office the original programmer for our custom systems is still on staff. The new VIEW system, which manages the entire facility, was written in 1996 and was programmed for full date fields and is Y2K code compliant. Our old tox lab data system, based on a DEC PDP11-70 will not survive the year 2000 transition because the hardware and operating system are both non-compliant with no hope of being made compliant due to obsolescence. Fortunately we have replaced this system with a field tested Y2K compliant product, programmed by one of our staff, called TOXLAB-PC All our PC-interfaced instrumentation is not yet Y2K compliant. Compliant systems will include the new data base software, TOXLAB-PC and upgrades to our HP 5970/5890 MSD, 6890 GC and UV/Vis systems. However, even if we did not upgrade, sample processing will still be possible in the year 2000, only that all date related fields will be incorrect. Hewlett Packard, Inc., Perkin-Elmer Inc., Varian Inc. and similar companies have Internet sites that deal with Y2K. Costs of compliance may vary from hundreds to thousands of dollars. There is not going to be a "silver bullet" to deal with Y2K. Only a methodical evaluation of current software and hardware will provide the required solutions for Y2K.
Earthbeat - 5/12/98 Year 2000 Computer Problem
The environmental effects of the year 2000 problem could be devastating and some say it poses the greatest threat to the environment in the history of
http://www.abc.net.au/rn/science/earth/stories/s17813.htm

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

21-40 of 104 Back | 1 | 2 | 3 | 4 | 5 | 6 | Next 20