Silicon Investor (SI) -- The First Internet Community

STOCKTALK

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor. We ask that you disable ad blocking while on Silicon Investor in the best interests of our community. If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.

Technology Stocks : Discuss Year 2000 Issues -- Ignore unavailable to you. Want to Upgrade?

To: John Mansfield who wrote (1355)	3/30/1998 4:42:00 PM
From: John Mansfield	Read Replies (2) \| Respond to of 9818

Hamasaki: 'got to identify the 10% of systems that are absolutely essential and just fix those. Got it?' On C.S.Y2K _________ <SNIP> 'Baloney? Cr*p? Yes, the internal processing has very little to do with loan amortization. Bringing up mortgages, payoffs, etc. reveals a lack of understanding of enterprise systems. The real business rules are very complex. That's why banks are spending hundreds of millions of dollars each to solve their Y2K problem.... and that's just the banks that have recognized it. I don't like having to slap people around but come on folks. Denial ended last year. We're in panic now... didn't you get the memo? Y2K is not an exercise, it's not a survivalist nut-case's wet dream. It's real, the systems are going to break, and at this date, there is no way to stop it. Please, we have 642 days left. Let's not try to think this one out. We've got to identify the 10% of systems that are absolutely essential and just fix those. Got it? There's enough time to fix and test 10%! Pick them, get started. ...well maybe 20% if you can hold onto the the King-Geeks, the superprogrammers. Some shops can't fix anything in the time left. First they'd have to find the source code. Then they'd have to 'gen a compliant version of the operating system, install compliant compilers and databases.... oops, 2001... Game Over Man. cory hamasaki

To: John Mansfield who wrote (1355)	3/31/1998 1:28:00 AM
From: John Mansfield	Respond to of 9818

Suite Applications Face Year 2000 Woes (03/30/98; 12:01 p.m. EST) By Lee Pender, Computer Reseller News '. It's that you could run projections that will look plausible and actually be quite wrong." '"The most critical area is the finance groups in a company," Kirby said. "Look at a 30-year mortgage. Most companies do an enormous amount of calculations in Excel, and those calculations have date dependencies in them. It's very subtle, but it's a business risk." ' techweb.com

To: John Mansfield who wrote (1355)	3/31/1998 12:50:00 PM
From: John Mansfield	Respond to of 9818

critical Y2K dates 'There are at least ten critical Y2K dates in the next two years. Mark these on your calendar, and be ready! Many thanks to the various folks on this newsgroup for posting these dates. I've merely complied them into one handy reference. July 1, 1998: First day of fiscal 1999 for 46 of the 50 States October 1, 1998: First day of fiscal 1999 for the Federal government. January 1, 1999: Limited software failures? April 1, 1999: First day of fiscal year 2000 for New York (State), Canada, and Japan. September 9, 1999 (9/9/99): It has been debated that there might be limited software failures (Sometimes used as a code for infinity or as a trigger for tests or shutdowns.) October 1, 1999: First day of fiscal 2000 for the Fed Gov. January 1, 2000: is "La manana grande". This will be day that the biggest disruptions will likely occur. Monday, January 3, 2000: The first working day after the big rollover. January 10, 2000: A "brick wall" for some software? February 29, 2000: A leap day that won't be recognized by non-compliant software. James Wesley, Rawles _________ From: (James & Linda, Rawles) Newsgroups: comp.software.year-2000 Subject: Y2K Critical Path Dates Date: Sat, 28 Mar 1998 13:25:02 -0800