Home  - Basic_Y - Year 2000 Computer

Books Baby Camera Phones Computers Games DVD Electronics Kitchen Magazines Music Garden Software Tools Toys Video Apparel & Accessories Jewelry & Watches Musical Instruments Health & Personal Care Beauty Sports & Outdoors Office Products

e99.com Bookstore

Images

Newsgroups

41-60 of 197    Back | 1  | 2  | 3  | 4  | 5  | 6  | 7  | 8  | 9  | 10  | 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)

YEAR 2000 COMPUTER PROBLEM, THE: A GUIDE FOR SMALL AND MEDIUM-SIZED BUSINESSES by JONATHAN WHELAN, 1997 Congress seeks Y2K shield.(year 2000 computer glitches): An article from: Strategic Finance by Stephen Barlas, 1999-05-01 Y2K losses may spark coverage battle.(insurance coverage losses related to Year 2000 computer problems)(Product Trends): An article from: National Underwriter ... & Casualty-Risk & Benefits Management by Susanne Sclafane, 1998-01-26 A mad, mad millennium?(Security Spotlight)(banking sector's management of anticipated problems related to the Year 2000 computer glitch): An article from: Security Management by Michael Gips, 1999-01-01 The Y2K problem: where is it covered in ISO's CGL forms? ('year 2000' computer problem; Insurance Services Office; commercial general liability): An article ... & Casualty-Risk & Benefits Management by Peter Price, 1997-10-13 It's Never Too Late To Begin Preparation To Manage Year 2000 Computer Exposures.(Brief Article): An article from: National Underwriter Property & Casualty-Risk & Benefits Management by Gregory A. Maciag, 1999-06-14 Asian insurers said to lag in Y2K compliance.(year 2000 computer compliance): An article from: National Underwriter Property & Casualty-Risk & Benefits Management by Lisa S. Howard, 1998-05-04 New systems and system upgrades. (Broward County, FL's preparation for the year 2000 computer transition problem): An article from: Government Finance Review by John Pryor, Jennifer Woods, 1998-06-01 RMs to ask vendors: 'ready for 2000?' (year 2000 computer problem)(Special Report: Risk Management Services): An article from: National Underwriter Property & Casualty-Risk & Benefits Management by David M. Katz, 1997-05-19 Y2K coverage debate could rival A&E.(Year 2000 computer problems, asbestos and environmental litigation)(Special Report: Product Trends): An article from: ... & Casualty-Risk & Benefits Management by Susanne Sclafane, 1998-01-26 No problen, mon.(managing the year 2000 computer problem): An article from: Doors and Hardware by Donna Munari, 1999-02-01 Year 2000 computer problem posed for legal avalanche, warns accounting tool maker. (SBT Accounting Systems): An article from: Software Industry Report A Survival Guide for the Year 2000 Computer Glitch: For City Dwellers by Lynne Walters, Connie Duke, 1999-01 Year 2000 poses liability exposures.(year 2000 computer problems and business): An article from: National Underwriter Property & Casualty-Risk & Benefits Management by Vito C. Peraino, 1997-02-03

lists with details

41. The Year 2000 Computer Problem - Countdown To Destiny!
    The year 2000 computer Problem Y2K INDEX of TOPICS Overview; Year 2KCompliance; We will get it fixed in time, won't we? What's the Rush?  
    http://www.club2000.com/y2k/y2krush.html
    
    Extractions: While many people are eagerly awaiting January 1st, 2000 to see if anything will actually crash, there needs to be an awareness that this is not only a one day problem. Since software and hardware that is involved in projections and demographic data we are surely going to need to be up to speed at least one year in advance. According to the Gartner Group, while 40% of the time and resources might be spent on analysis of the problem and modification of the situation, another 45% of the time is spent on testing, training, disaster recovery and documentation. This means that companies cannot START their fixes in the year 1999, they need to be on it by mid 1998 to have a good chance of minimizing the problems. We are less than 380 days away before this date arrives.

42. Year 2000 Computer Problem
    Winter 1997'98 Technical Update Mainframe News. year 2000 computerProblem. In a nutshell, the year 2000 computer Problem is that  
    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

43. 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
    
    Extractions: General Interest 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

44. The Tenagra Corporation - Media Center - "Year 2000 Computer Crisis"
    Clifford Kurtzman, The Tenagra Corporation, Cliff.Kurtzman@Tenagra.com, 281/4806300.INTERNET INFORMATION CENTER ESTABLISHED ON year 2000 computer CRISIS.  
    http://www.tenagra.com/releases/pryear2000.html
    
    Extractions: ON YEAR 2000 COMPUTER CRISIS Brampton, Ont, Canada, May 1, 1995 - Peter de Jager and The Tenagra Corporation are pleased to announce the opening of the Year 2000 Information Center on the Internet World-Wide Web. For many computer and software systems, the year 2000 will bring a host of problems related to software programs that record the year using only the last two digits. This faulty standard will cost the worldwide computer community billions of dollars in programming effort. The Year 2000 Information Center allows Internet users to get the latest facts and information on the Year 2000 computer crisis, and provides a forum for the discussion of possible solutions. Hosting a continually updated clock showing the number of years, days, hours, minutes and seconds remaining until the Year 2000, the Information Center also provides free access to information made available by vendors and service providers that offer consulting and solutions. The Year 2000 Information Center

45. Year 2000 Computer Liability Conference
    Who's Reponsible When Mission Critical Computer Systems Fail? A GroundbreakingEvent Series Focused on Year 2000 Liability Implications.  
    http://www.tticom.com/y2k-liability/

46. Year 2000 Computer Liability Conference - Overview
    Announcing the year 2000 computer Liability Conference Who’s ResponsibleWhen Mission Critical Computer Systems Fail? LOS ANGELES  
    http://www.tticom.com/y2k-liability/overview.htm
    
    Extractions: July 20-21, 1998 A Groundbreaking Event Series Focused on Year 2000 Liability Implications. Corporations are spending close to $600 billion worldwide to furiously find, fix and test billions of lines of code affected by the Year 2000-date change. But do you think that on the first second of January 1, 2000 systems will be crash free? Think again. No matter how much companies are spending, the threat of systems not being able to function are staggering. The fact is, unless the process of debugging critical programs is not well along by now, it may be too late to fix. According to an article in Business Week , law firms are expecting billions of dollars in litigation. That's why now is a critical time for lawyers, corporate in-house counsel, executives and risk managers to gather the information they need to protect their company and customers and avoid potential lawsuits. Attend the Computer Liability Conference and take the first step in minimizing legal risk and maximizing recovery.

47. Year 2000 Research Center - The Year 2000 Computer Problem
    The year 2000 computer Problem On January 27th, 2000 Gary Beach, CIO Magazine's publisher,testified before congress on the fallout from Y2K and its effect on  
    http://www.cio.com/research/y2k/edit/020300_garyfed.html
    
    Extractions: On January 27th, 2000 Gary Beach, CIO Magazine's publisher, testified before congress on the fallout from Y2K and its effect on the future of IT. Prepared Testimony of Gary Beach Publisher CIO Magazine Before the House Science Committee Subcommittee on Technology and the House Government Reform Committee Subcommittee on Government Management, Information and Technology. My name is Gary Beach, and I am the publisher of CIO magazine, the leading publication for chief information officers (CIOs) and other senior executives who use information technology (IT) to improve their businesses. CIO provides its readers with current information and case studies on the effective uses of technology. Our readers work in major corporations, including Fortune 1000, and in federal, state and local government agencies. My Year 2000 expertise includes daily dialogues with business and technology executives as publisher of CIO and my work on the steering committee of YES Corps, an international network of volunteer Y2K experts supported by the International Y2K Cooperation Center, the United Nations and the World Bank. The subject of my testimony is Lessons Learned.

48. Harvard Seeks To Swat Year 2000 Computer Bug
    Harvard Seeks to Swat year 2000 computer Bug. By Alvin Powell. The year 2000is coming and Harvard's computer specialists are preparing to meet it.  
    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.

49. Year 2000 Computer Bug Demands Attention Today
    year 2000 computer Bug Demands Attention Today By Alvin Powell. Specialto the Gazette. It's Jan. 3, 2000, the first day back to work  
    http://www.news.harvard.edu/gazette/1997/11.13/Year2000Compute.html

50. Y2K For Conmen The Year 2000 Computer Problem What Every
    What's the Big Deal About Y2K? The year 2000 computer Problem What Every ConmanNeeds to Know and How to Keep Him/Herself and his/her Family in the Money.  
    http://www.scorpioncity.com/y2kconmen.html

51. 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.scorpioncity.com/y2kwomen.html

52. Year 2000 Computer Problem And Health Care Industry
    Testimony on year 2000 computer Problem and Health Care Industry by Nancy_AnnDeParle Administrator Health Care Financing Administration US Department of  
    http://www.hhs.gov/asl/testify/t980723c.html
    
    Extractions: Administrator Health Care Financing Administration U.S. Department of Health and Human Services Before the Senate Special Committee on the Year 2000 Technology Problem July 23, 1998 Chairman Bennett, Vice Chairman Dodd, distinguished committee members, thank you for inviting me here today to discuss my highest priority. We must assure that the more than 70 million Medicare and Medicaid beneficiaries experience no interruption in services because of the Year 2000 computer problem. We also must assure that the approximately 1.6 million Medicare and Medicaid providers continue to receive prompt and efficient payment for their services. PROGRESS I am committed to doing everything possible to address this issue, and we are making substantial progress in addressing the Year 2000 problem. Since I became HCFA Administrator in November we have: completed renovation of five of our six standard systems; completed renovation of 24 of our 37 most critical internal systems; initiated testing of renovated systems;

53. 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
    
    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.

54. The Year 2000 Computer Bug- Identifying Potential Impact On Sub-Saharan Africa -
    No. 47 November 1999. The year 2000 computer Bug Identifying PotentialImpacts on SubSaharan Africa. The Year 2000 (Y2K) computer  
    http://www.worldbank.org/afr/findings/infobeng/infob47.htm
    
    Extractions: Identifying Potential Impacts on Sub-Saharan Africa The Year 2000 (Y2K) computer bug could potentially affect digital control systems and computer hardware/software that rely on date-dependent calculations for their proper functioning. A considerable level of automation and computerization has taken place in Sub-Saharan African (SSA) countries in recent years. Although the level of automation may be lower compared with more technologically advanced countries, the relative reliance of SSA countries on these systems is generally higher. This is partly because a limited number of systems process the information required by most public agencies. Examples include treasury, customs, central bank, pension, and other similar public sector operations, many of which do not have alternative backups in case of system failures. Any major failures in these systems could potentially lead to economic and social hardships for affected countries, resulting in an undesirable impact on the country's development. Due to the complexity of both national and cross-border interdependencies among various sectors, the longer term effects of potential Y2K failures in certain critical operations on the national economy are often ignored. The Knowledge and Learning Center in the Africa Region of the World Bank has developed a potential risk exposure profile for SSA countries based on a set of indicators from various critical sectors. These indicators provide a better picture of the potential Y2K risk exposures, and the significance of certain operations for the economy. The salient features of the findings from these indicators are discussed below.

55. The Year 2000 Computer Crisis -- What To Do NOW?
    The year 2000 computer Crisis What To Do NOW? By Warren S. ReidThe various independent surveys from SIM and Anderson Consulting  
    http://www.shk-dplc.com/cfo/articles/crisis.htm
    
    Extractions: By Warren S. Reid The various independent surveys from SIM and Anderson Consulting Worldwide and Peter deJager keep telling us the same thing - that only 20-30% of all US companies have begun to inventory their systems and perform any risk assessment steps to address their Year 2000 problem. Worse, less than 10% have actually started fixing their code. While the rest of the world, and your company is catching up, there are things that you can - and must - do right NOW to help your company address the problem and withstand the inevitable onslaught of litigation that is allegedly making some attorneys salivate. The Economist in its cover story in its October 4th-10th, 1997 issue entitled "The Millennium-Bug, Muddle" quotes the estimated cost to the world's companies and governments of fixing the problem (including fixing the errors, lost productivity from those systems that fail, and the cost of liability lawsuits) at - take your choice: Gartner Group $600 billion; Technology Research Reports, a California market-research firm, $2 trillion ; and Boston's Software Productivity Research at $3.6 trillion. It's getting pretty ridiculous and over the top.

56. FCC Announces Initiatives On Year 2000 Computer Date Isuue
    Please remember to bookmark our site!) 9822. FCC Announces Initiativeson year 2000 computer Issue. The Federal Communications Commission  
    http://www.ncs.gov/n5_hp/Customer_Service/XAffairs/NewService/NCS9822.htm
    
    Extractions: Note: If you click on the http://www.fcc.gov/year2000/ below, you will be leaving the NCS Homepage. Please remember to bookmark our site!) 9822. FCC Announces Initiatives on Year 2000 Computer Issue The Federal Communications Commission (FCC) announced a series of initiatives April 17 to raise awareness within the various communications industries of the Year 2000 computer date change problem. Commissioner Michael Powell, in connection with his role as FCC Defense Commissioner, will represent the FCC on the President's Council on Year 2000 Conversion. President Clinton established this council February 4, 1998. As part of its efforts, the FCC launched a special Internet site on the World Wide Web to provide information for consumers and industry on the Year 2000 date change problem: http://www.fcc.gov/year2000/ . In addition, an FCC task force formed March 20, 1998 is coordinating efforts by each FCC Bureau to provide information for consumers and industry on the Year 2000 date change problem. The FCC is also coordinating an outreach effort and working closely with state Public Utility Commissions and Public Service Commissions.

57. FCC Announces Initiatives On Year 2000 Computer Date Issue
    FCC ANNOUNCES INITIATIVES ON year 2000 computer DATE ISSUE; COMMISSIONER POWELLTO REPRESENT FCC ON PRESIDENT'S COUNCIL ON YEAR 2000 CONVERSION .  
    http://www.fcc.gov/Bureaus/Miscellaneous/News_Releases/1998/nrmc8027.html
    
    Extractions: The FCC today announced a series of initiatives to raise awareness within the various communications industries of the Year 2000 computer date change problem. Commissioner Michael Powell, in connection with his role as FCC Defense Commissioner, will represent the FCC on the President's Council on Year 2000 Conversion which was established by President Clinton on February 4, 1998. The FCC today will launch a special Internet site on the World Wide Web to provide information for consumers and industry on the Year 2000 date change problem: http://www.fcc.gov/year2000/

58. Republican U.S. Not Ready For Y2K
    With two years to go, the United States is still unprepared to deal with the year 2000 computer bug that threatens to wreak havoc in everyday lives, a Republican congresswoman said. News.com  
    http://www.news.com/News/Item/0,4,17783,00.html?st.ne.fd.mdh

59. PEC Recommendation To President Clinton On Year 2000 Computer/Software Issue
    The Council recognizes that you and the Vice President are taking an active leadershiprole in addressing the year 2000 computer/software issue and its  
    http://www.ita.doc.gov/TD/PEC/y2klttr.htm
    
    Extractions: Dear Mr. President: I am writing to you in my capacity as Chairman of your Export Council. The Council recognizes that you and the Vice President are taking an active leadership role in addressing the year 2000 computer/software issue and its potential impact on both government and private sector operations. Our specific concern is that given the interlinked world economy, more emphasis needs to be given to this problem in various upcoming high level international governmental meetings. Specifically, we recommend that this issue be emphasized at the upcoming APEC meetings this month. It is recognized that the cost to fix all the year 2000 associated problems will be significant. Although we recognize that this issue must be dealt with in the context of the economic issues facing many APEC member nations, we recommend that all countries focus on priority areas such as the financial, transportation, telecommunications, utilities, and medical services sectors. Sincerely

60. FCC Telcos To Kill Y2K Bug In Year
    Despite concerns by members of Congress and industry observers, U.S. phone carriers plan to rid themselves of the year 2000 computer bug in less than a year, according to a member of the Federal Communications Commission. News.com  
    http://www.news.com/News/Item/0,4,23265,00.html?st.ne.fd.mdh

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

41-60 of 197    Back | 1  | 2  | 3  | 4  | 5  | 6  | 7  | 8  | 9  | 10  | Next 20