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 : AUTOHOME, Inc -- Ignore unavailable to you. Want to Upgrade?

To: RocketMan who wrote (3774)	1/2/1999 9:53:00 PM
From: Frank A. Coluccio	Read Replies (1) \| Respond to of 29970

<-----OT------> RocketMan, The following is either inconsequence, or incontinence, you decide. It addresses your previous post to me concerning Y2K. There has been an extraordinary amount of Y2K coverage on CNN, CNBC, and CSPAN this weekend. Appropriate, I think. I have staff working at one of the nation's top banks on Y2K carrier issues. We're working side by side with Bellcore there, as well as with several other consultancies and in house staff. Since early '98 the number of identified problem spots yet to be remediated has gone up, not down, with the majority of them being in the PTTs. Some of the ILECs are dragging their feet w.r.t. some network management system changeouts, but nothing that seems to be of dire consequences right now. Admittedly, however, we are getting very sketchy information, at best, concerning SS7/AIN and DCS platform preparedness. The OSSes that used early vintage SUNW workstations, ironically, have all been remediated, though, and the carriers are not hesitant to disclose those facts. This causes us to read between the lines. The bank's lines go to 80 some odd sovereign nations. This is going to be quite a haul, since many of the foreign PTTs [mainly the smaller ones in the southeast Asian, and some of the African countries, don't even have a clue yet at the operations levels, as to what they've got in the way of vulnerability, much less a bona fide program installed to track their own progress. >>I suspect the first real world instance will lead to a feeding frenzy by the press, and depress tech stocks for a week or two, until the press moves on to some other crisis.<< I don't know about that. In those cases where patches are being used, they may get through the first months of 2000 alright, but as you've indicated yourself, 010100 is not the only date that is vulnerable. And the final remediation, beyond the patch phases that are being implemented now, are said to possibly last another five to ten years, in many cases, before native code is either rewritten or systems are replaced entirely. The one system that I am most intimately involved with at this time is one that has been growing modularly, in stages, for over twenty years, being ported from time to time to the next level up in enterprise mainframe architecture/OS. I dont think that we're in for a flash cut here, in fact I'm sure we're not. It wont be over for quite a few years, at best. Regards, Frank C.