eWeek Microsoft Watch
Advertisement
Advertisement
May 21, 2006 8:21 AM

Vista's Make Or Break Moment



It's the hour of reckoning for Windows Vista.



After five years of course changes, false starts and a host of beta and Community Technology Preview (CTP) builds, Microsoft is set to deliver a broad-scale build of Vista to two million testers. Microsoft is likely to drop the build – known by multiple names, including the consumer Vista CTP and Vista Beta 2 – as early as this week at the Windows Hardware Engineering Conference (WinHEC) in Seattle, according to company watchers. (Around the same time, Microsoft also is likely to release Office 2007 Beta 2, the next major milestone of Microsoft's next-generation desktop suite, as well as Beta 2 of Longhorn Server.)



While the exact Vista release date is fluid, the facts are not--this cut of Vista needs to be more solid than a year's worth of previous builds from Microsoft. Even the most recent Vista builds, including two interim CTPs delivered during the past couple of months to the company's squad of elite beta testers, known as Technology Adoption Program (TAP) partners, have suffered from a variety of performance and compatibility problems, according to interviews with eight testers.

"There's too much variation in performance from one build to another," said Brandon LeBlanc, a Portland, Ore.-based Vista tester and contributor to a number of Windows community sites, including MSTechToday, LonghornBlogs and LiveSide.Net. "The changes they are continuing to make at this stage disrupt performance too much. You'd imagine they would have gotten past this stage by Beta 2."



Testers said that if the next build of Vista doesn't improve dramatically, Microsoft will have a tough time sticking to the outline the company issued in late March. Microsoft's current timeline calls for the company to release the final Vista code to manufacturing this summer or fall, allowing customers under volume-licensing agreements to get their hands on the code by November, 2006. Microsoft executives have maintained that the dual launches of Vista and Office 2007 is on for January 2007, when code for both products will be available to all customers.

Indeed, doubters of Microsoft's ability to hit its timeline aren't hard to find. Gartner in a research note earlier this month said Vista's availability could be pushed back at least by a quarter.



"Here is what any team has to get absolutely right in order to call a build Beta 2: the build has to be solid enough that testers can run it to perform their day-to-day work," said Michael Cherry, an analyst with Directions on Microsoft, based in Kirkland, Wash. "If the software is not stable enough to run in day-to-day use then it will delay testing, which delays testers finding bugs."



Sounds straightforward, but Microsoft employees and corporate testers running Vista as their primary operating system report the product is not "production-ready." Even long-time Vista testers and Windows community members, who know the intricacies of Microsoft products as well as the Redmond, Wash.-based software makers own developers and testers, are having problems with the latest builds.



While it's tricky comparison between 2001's Windows XP and Windows Vista – given the differences in the size and the complexity of the code bases– testers noted that Vista doesn't seem to be as solid and ship-ready as XP was at the Beta 2 juncture.



"With "Whistler" (Windows XP), you could basically run the OS (operating system) as a near-production based OS," said Brad Wardell, president and CEO of Stardock, Corp., a Plymouth, Mich., software vendor. "With Windows Vista, the networking issues, performance, and compatibility prevent users from making it their main OS."

Among the issues Microsoft's next build will need to address:

  • Networking: Vista networking is a sore spot with a number of Microsoft's hardcore testers, not just Wardell. As is true on a variety of Vista fronts, especially security and systems management, Microsoft has tuned the product users not administrators. And power users are none too happy about that.

    Memory, Driver Issues Continue to Plague Testers, Too.

    Next Page: Vista's Make or Break Moment


    "The network panel is a nightmare if you attempt to do anything mildly complex," said Carlos Echenique, Site Owner and Editor-in-Chief of the Miami, Fla.-based PlanetX64/PlanetAMD64 Windows community sites. "While the panel is great for simple setups, power users will start committing seppuku if they have to do any real troubleshooting."



    Stardock's Wardell agreed.



    "Beta 2 needs to make sure its networking is nailed down," said the Vista tester and operator of the WinCustomize Windows community site. "The betas of Windows Vista have had atrocious issues with networking being reliable. Without the basic features of a modern OS working, people won't run it and that will mean a lot less feedback."



  • Driver and application compatibility:
    For many testers, compatibility is at the top of their Beta 2 wish lists.



    "Application compatibility, leastways for the top 500 shipping applications," needs work, said John Obeto, managing partner and chief technology officer with Logikworx, a Marina Del Rey, Calif.-based solution provider specializing in systems and network security. Obeto also is a Vista tester and runs the AbsoluteVista community site.

    "Most of my personal issues with Vista are currently caused by driver issues," added Michael Reyes, a principal with the Brooklyn, NY-based HardwareGeeks.com community site. "Between the sound stack and video drivers having to be redone a lot of the available library of drivers are very rough around the edges and do cause lock-ups."



    Planet X64's Echenique, with his interest in 64-bit support, also cited driver support as in need of improvement.



    "Overall stability, especially in the x64 versions, could be improved. Now, this could be caused by marginal drivers. Lord knows that x64 is treated as a second-class citizen regarding drivers," Echenique said. "But I have found that the UI (user interface) hesitates sometimes. This was still present as of Build 5308," the CTP build Microsoft released in February.



  • Memory Ceilings and "handles":

    Wardell said he has two primary issues with Vista related to memory and "handles," a type of computing resource that various programs such as email and desktop search use.

    As for the memory issue, Wardell said it's becoming increasingly difficult to add memory to boost performance. "We are now bumping up against the two gigabyte limit," said Wardell, adding that if Vista needs more than that to operate at a high level there will be problems. As for the two gig reference, Wardell noted that while 32 bit processors can access four gigabytes of memory per process in theory, the upper two gigs are reserved.



    "Windows Vista uses considerably more memory than Windows XP -- about twice as much and there is not much reason to think this amount will significantly change by release. Realistically, until 64-bit machines become the norm, the two gigabyte limit is going to be a problem," he said.

    The handle issue could also be key. Wardell estimated that Windows XP boots using about 3,000 handles compared to 15,000 for Vista. He has found that Windows slows down when handles hit 15,000 and 25,000.

    Whether or not Microsoft gets to these myriad and substantial fixes and tweaks by the time the Beta 2 build hits should be apparent soon. But Directions on Microsoft's Cherry said Vista may illustrate that the company has to revamp its entire development process.



    "I think the problems they (Microsoft) are having relate to not getting to a feature-complete state earlier," Cherry said. "It seems like they were still accepting changes and new additions very late in the process."

  • TrackBack

    TrackBack

    http://www.microsoft-watch.com/cgi-bin/mte/mt-tb.cgi/4986

    Comments (1)

    Keith Risler :

    All this talk of varying flavors of Vista, Pay As You Go MS software rental, busy Betas and so forth leaves me wondering if we aren't in effect being forced rather upmarket by all this new MS software and OS glue.On my main desktop system, the MS Vista adviser software informed me that I will need to buy one of the top-end Vistas just to get the features I use now in little ole' XP Pro. Moreover my main PC will need a new video card to run Vista in a full-featured way. As for my laptop and two other systems, evidently they have to be thrown away as they will not run Vista well if at all.The real question is not whether all this Beta ware is now working okay at its present Beta level; the real question is whether most extant software will run under Vista. My understanding is that the user rights changes Vista requirea to run an app are changing, and that this change will deep-six many extant apps unless updates for them are issued.I would like to see articles assessing the opportunity cost of Vista in this context, not whether the Betas of newly revised software packages are "getting there" so to speak. All this new software and hardware will have to offer a huge payback of some kind to justify the cost.And where is that payback? It sure is not in any environmental gains.We should be asking in the context of global warming whether laws requiring OS and software vendors to make all software compatible with extant hardware would be appropiate. Do we really need to waste energy building and shipping new computers that use still even more electricity than the ones they replace, just to get that Vista Aero "cool new look?"

    Post a Comment

     
     


    RSS Syndication

    Most Recent Blogs


    Advertisement
    Advertisement
    Microsoft Watch     Contact Us | Advertise | Site Map
    Ziff Davis Enterprise