Slashdot Mirror


Microsoft Says Windows More Reliable Than Sun

Anonymous Coward pointed us to a microsoft.com page that claims, "Major customers, such as Quote.com, are switching from Sun to the Microsoft® Windows® platform because it offers better reliability." That's not the only reason given here to switch to a Windows environment, and apparently there are more to come every day until Windows 2000 is launched. Another direct quote: "Want more facts? Return to this page tomorrow for your daily dose of reality."

1 of 641 comments (clear)

  1. I have used Win2k and seen these issues by soldack · · Score: 5

    As a device driver developer, I have been using every weekly build of Win2k since before Beta2. I can tell you for a fact that Win2k is buggy and unstable. I was at the Microsoft Plugfest, where system vendors and device vendors get together and try running their stuff together under Win2k and WinMe (Windows Millenium). Build 2195, the build that went gold was cut after the first day of the plugfest, due to a major bug that had to be fixed. Lots of bugs were reported during the following days of testing. NONE of these low level, at the core of OS, in the kernel type of bugs were fixed for the gold release. We were told that they would go into SP1. In fact, the cut off date to get a fix into SP1 was the end of december. My group has already submitted Plug 'N Play issues that will not be fixed until SP2 at the earliest. This thing is not ready for prime time!
    At the plugfest, Microsoft's engineers were often stumped with problems that only a small hotel full of only three days or so of testing; imagine what millions of users in months of continuous running will find. Win2k's bug list is so large that you have to search for your problem at their site rather than all the known issues being made public through a definitive list. I for one would want to read that list before I bet my e-business site on it.
    Try running a check build of Win2k and ready the output from WinDbg. Note all of the errors flying by, filling WinDbg's 30,000 line buffer size. Try running WinDbg, the main graphical kernel debugging tool Microsoft ships. It is perhaps the worst piece of software ever made. Every version fixes one bug but creates another. MS's own pplugfest engineers would not use it. If it is buggy than what kind of drivers will it lead to? How about Visual C++, which all of Windows is build with? How can an OS be stable when the development environment that created it needed three service packs?!
    As for living in a heterogeneous lan, Win2k's Active Directory uses Dynamic DNS, which most other systems, including NT4, do not support. Although, you can get DDNS for Unix/Linux systems, it requires you changing all your other machines to work with Win2k.
    Win2k is very bloated! Look at the size of all the running modules in a base Win2k Pro installation; it is massive! Check out the minimum requirements; they are unbelievable!
    This isn't anti-microsoft, brainwashed by /. FUD; it is the result of years of low level study.

    --
    -- soldack