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.

Politics : Ask Michael Burke -- Ignore unavailable to you. Want to Upgrade?

To: Knighty Tin who wrote (36312)	11/15/1998 7:52:00 PM
From: Ilaine	Read Replies (1) \| Respond to of 132070

Hi Mike, I like Homer's (nuclear reactor operator) solution posted earlier this week. Tell your computer it's 1969. Or pick your favorite year. Only programs it'll mess with are Quickbooks and Turbotax, and I can do them on the new Compaq, which is Y2K compliant. Guess it won't work for mega-corporations, but for small businesses, other than messing with dates in accounting programs, why not? CB P.S. My brother-in-law the Cobol programmer, who works for a temp firm, says that he is just about done with his Y2K programming, the temp co. is going to place him doing something else. P.P.S. Caught your letter in Barrons. "You're so vicious."

To: Knighty Tin who wrote (36312)	11/15/1998 11:08:00 PM
From: Mary Cluney	Read Replies (3) \| Respond to of 132070

MB, >>>I know that there are also hardware problems with Y2K, but they are in few systems and most can be overcome without tossing out the entire box. If you look at Motorola's budget for Y2K, which hit the news today, there is almost nothing allocated to hardware purchases. Internal costs are 70% of their spending, outside software vendors and consultants/bodies nearly 30%. I think that will be the type of thing we will see for most large cos., not new system buys on a massive scale.<<< You are right in so far as what the media is covering concerning the Y2K problem. It is 99% software related - very little if any is hardware related. There is an estimate (from the Gartner Consulting Group) that the immediate Y2K problem involves around 600-800 billion lines of computer code. Seventy percent of that is written in Cobol - most of the others are in Fortran, Aseembler, PL1. Very little of it is in the modern languages - C, C++, Basic, Java et al. The remediation just to prevent system crashes is estimated at $1 per LOC. Unfortunately, after spending the money on consultants in fixing the 420-560 billions LOC that is written in Cobol what you have left are programs that will work in the year 2000 that was orginally designed for IBM Systems 360, 370, 8100, NCR 8500, HP3000, VAX's, UNYSIS, WANG, PRIME, Burroughs, Amdahl, Fujitsu, Siemans, Nixdorfs, and others. These are or were terrific systems - but most have discontinued production and not many people are trained to maintain these older systems. Further, they are characterized by what they are lacking. They lack the GUI, ICONS, Mice, Pull Down Menus, and the color that most of your people have come to know as computing. Most of these systems are still character based. Just in order to use many of these systems, Users have to be specially trained to learn the codes and other conventions that were setup to start these systems. Most of the stuff was not intuitively obvious. As you can see, (perhaps), these may initially be characterized as a software problem, but they will very quikcly become a hardware problem - perhaps not immediately - but over time. Sincerely, Mary