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 : All About Sun Microsystems -- Ignore unavailable to you. Want to Upgrade?

To: Michael L. Voorhees who wrote (34851)	8/29/2000 12:15:13 PM
From: Rob Young	Respond to of 64865

"Anyway, I'm extremely happy that this appears to have been a non-issue (or at least relatively minor) as far as SUNW's stock price and I'm glad the issue is out in the open to all stakeholders and will thus surely be fixed rapidly (if it hasn't already been). " I wouldn't use the term rapid. Go back to the ComputerWorld article: computerworld.com "Gartner plans soon to release an advisory on the memory component issue, updating one released in November, because of continued and "frequent client complaints of persistent downtime" caused by the problem." The advisory isn't going away... it is being updated. There are many examples of problems out in discussion forums. Many of these of course anonymous. If you followed the Slashdot discussion yesterday, you might have found a couple of examples of the parity errors like these: My group runs a mid-size to large server farm at a (very) major ISP and we're constantly replacing processors that crash due to "Ecache Writeback Data Parity Error"s. We were told that even replacing the processor isn't a remedy because the new one is just as likely to eat itself as the old one if you left it in place (As far as they know.) In addition, the latest fix is a software patch that is supposed to massage the Ecache so that it never finds itself in the condition that they believe causes the error. Remember, they're still guessing at this point. 18 months later. How many of those 400Mhz are now used up with self-checks and Ecache scrubbing? Ever babysit a Sun E-anything on bootup? Not only does it cost the company tons of $$ in downtime (made more extreme by the long boot process), it also costs them $$$$/hour for their engineers to sit there and watch these things POST forever. I think the most aggravating part is how for all intents and purposes, Sun is now using the worlds largest enterprise sites as beta testers for it's product just like M$ uses the world to test it's software except that Sun expects us all to sign our voices away with the NDA so they don't look like a bunch of ..... (something bad that you wouldn't wanna be called)." I'm posting anonymously to protect my job and my employer. We have 3 E10000 and 7 E6000 systems in our production environment. All of them have had the problem. All of them have gone through multiple exchanges of CPUs, memory and system boards. We are seriously looking at switching hardware vendors at this time. We are looking at RS6000s as a possible replacement, but it would take a considerable amount of work to recompile all of our custom apps for their environment. We also have about a dozen S-390 mainframes and have been looking at Linux under OS390 too.. Either way, I think we are going to be getting rid of Sun. --- Impact on stock price? Not much. But I believe the impact on reputation may be more significant as the former NDA folks come forward and as employees jump ship and spill their guts to various forums. Rob

To: Michael L. Voorhees who wrote (34851)	8/29/2000 1:19:06 PM
From: Michael L. Voorhees	Respond to of 64865

"Ex-MicroSoft Employee Unix within the Evil Empire" slashdot.org "Windows 2000 too unstable to use within MSFT..."