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 : Formerly About Applied Materials -- Ignore unavailable to you. Want to Upgrade?

To: Katherine Derbyshire who wrote (20466)	6/16/1998 10:30:00 PM
From: Paul V.	Read Replies (1) \| Respond to of 70976

Katherine, >Y2K is strictly a software problem in that a gas valve doesn't care what year it is. However, most semi equipment is heavily overlayed with software, creating some exposure. If I had to hazard a guess, I would say that companies dealing with fab automation (robots, control software, etc) have the most Y2K exposure, and companies dealing with non-intelligent components (cassettes, some valves, etc) have the least. Everyone else is on a continuum. For any company, Y2K is a potential problem if they have the bug and it causes customers tolose product, but a potential opportunity if they've fixed the problem and their competitors haven't.< Big Bucks, and other engineers, can you give us info regarding the Y2K exposure that AMAT has or will have with the Y2K problem? Should we be concerned or has AMAT addressed this problem with their robotics, etc? Thanks. Paul V.

To: Katherine Derbyshire who wrote (20466)	6/16/1998 11:19:00 PM
From: Clarksterh	Read Replies (2) \| Respond to of 70976

Y2K is strictly a software problem in that a gas valve doesn't care what year it is. Actually, not completely true. The classic example is elevators, some of which will shut down if they haven't been serviced in x months. Strictly speaking they aren't running software, but instead are either running firmware or are using hardwired ASIC's. The point is twofold: 1) that even very mechanical devices can have a problem, and 2) it isn't always as simple as just modifying some code and downloading it. As for whether the company is addressing the y2k problem, they addressed that in the March 10Q (as all companies are now 'required' to do) as: The Company has commenced, for its information systems, a year 2000 date conversion project to address all necessary changes, testing and implementation. The "Year 2000 Issue" creates risk for the Company from unforeseen problems in its own computer systems and from third parties with whom the Company deals on financial and operational transactions worldwide. At present, the Company's internal systems, the ability of the Company's suppliers to address the "Year 2000 Issue", and the impact of the "Year 2000 Issue" on the programs which operate the Company's products have been identified as the primary areas of risk to the Company from the "Year 2000 Issue". Management continues to assess Year 2000 compliance issues. Significant difficulties with, or failure of, the Company's and/or third parties' computer systems could have a material effect on the Company's ability to conduct its business. Clark