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 : Novell (NOVL) dirt cheap, good buy? -- Ignore unavailable to you. Want to Upgrade?

To: Bob Howarth who wrote (21486)	3/31/1998 3:46:00 PM
From: ToySoldier	Respond to of 42771

Bob, It is not easy to get any answers to position from Microsoft on the Y2K problem and their code, but here is an excerpt from their own web site... "Windows NT 5.0 is an evolutionary, not revolutionary, release of the Windows NT operating system. While there are important new features in this release, version 5.0 will build on a proven system architecture and incorporate tens of thousands of bug fixes from version 4.0. Summary Microsoft agrees with Gartner that the installation of new operating system on the eve of Y2K may be a disruptive force. However, the answer is well-planned, rapid adoption of Windows NT, not delay. To be best prepared for the Y2K, Microsoft strongly recommends that customers should deploy Windows NT 4.0 today, evaluate the Beta version of Windows NT 5.0 this summer, and plan for deployment of Windows NT 5.0 after the final release. Rapid deployment of the Windows NT platform will enable the following: - Y2K-compliant platforms. Windows NT Server 5.0 beta 2 will be Y2K compliant upon release. And most applications designed for Windows NT Server are already Y2K compliant as part of the BackOfficer logo program." The page I have quoted to you on this posting is Microsoft's attempt to counter Gartner Group's recommendation. Being that it appears that NT5 is the answer to NT4's Y2K Readiness, Gartner Group's recommendations put a major dent into their solution for Y2K. The complete web site that this excerpt came from is: microsoft.com Microsoft's Year 2000 FAQ page is below, try to follow this and figure it out yourself if your Microsoft SW is 2000 Ready. In this page they state that they will not warrent that their products are Y2K Ready. From reading the page, they provide very little content on how the NT server operating systems are affected by Y2K. In one paragraph it appears that Microsoft is developing a 2digit-to-4digit conversion library. microsoft.com If you are a Microsoft customer I would be getting on the phone with the Microsoft powers that be and demand a commitment from them that either all their current software is Y2K certified or that an easy to understand and acceptable Y2K action plan for existing software will be provided very shortly. Novell's Year 2000 web site describes the certification testing that needed to be done and exactly how and what of their products need to be either patched or upgraded. Very easy to understand. I hope this helps. I'd be interested if anyone else has heard of or better understands what a Microsoft customer must do to be sure that all their NT servers are Year 2000 Ready. ToySoldier

To: Bob Howarth who wrote (21486)	4/1/1998 1:27:00 AM
From: Scott C. Lemon	Read Replies (3) \| Respond to of 42771

Hello Bob, > NT 4 is not Y2K compliant? Could you be more specific? Thanks. After spending hours trying to find the straight answer, I think I give up. Here's a starting place: microsoft.com If they are compliant, they sure aren't bragging about it! I've looked around to try and find the "Simple Guide to NT Year 2000 Compliance" ... but the closest that I could come was: microsoft.com ... and although I would think that one of the most frequently asked questions would be "Is NT v4.x compliant?" it didn't seem to make the list! ;-) Scott C. Lemon