News

Microsoft Appeases Windows 7 Beta Testers

Microsoft's technical team on Thursday reported progress on improvements to the beta version of Windows 7, assuring testers that the team really cares about user feedback. As if to appease a clamorous horde, Program Manager Chaitanya Sareen provided a long list of changes made in response to user feedback.

The tone had initially been set by Steven Sinofsky, Microsoft's senior vice president for the Windows and Windows Live Engineering Group. In Microsoft's Engineering Windows 7 blog on Wednesday, Sinofsky described the magnitude of the problem.

"There over a couple of million people using the beta and if each one, or for that matter just one out of 10, have some unique change, bug fix, or must-do work item, we would have literally years of work just to make our way through that list," he wrote.

Microsoft has frozen the general feature set of Windows 7 for this beta testing period. However, the engineering team is still refining some of those features. Sinofsky acknowledged the pressure to "stop changing the product and ship it," along with the engineering consequences and cost considerations of making deep changes to the operating system.

"We write specifications and have clear views of features (scenario plans, prototypes, and so on) because we know that as the project progresses the cost of making big changes of course goes up," he wrote. "The cost increases because there is less time, but also because big change late in the cycle to a large system is not prudent engineering."

Most of the changes described in the Engineering Windows 7 blog were minor tweaks to the user interface. One of the non-user-interface improvements was better support for devices in Device Stage, which is Microsoft's visual display of hardware devices recognized by Windows 7.

"Although Windows already supports tens of thousands of devices, customer feedback on the Beta introduces even more device support in RC [release candidate] via the new Device Stage experience," the blog explained.

Microsoft has consistently said that Windows 7 will support hardware if the drivers for that hardware were compatible with Windows Vista. However, at least one report, which tested a Vista upgrade to Windows 7 Beta without a clean install, has questioned that assertion.

The technical team acknowledged a problem with audio hardware working with the Windows 7 Beta. Not all of the 26,000 custom audio drivers are currently available on Windows Update, the blog noted. In response, Microsoft is tightening up its testing program with the release candidate version.

"The Release Candidate tightens the Windows Logo test to better ensure clean install delivers baseline functionality for speakers and microphones," the blog asserted.

The engineering team also claims to have squashed some bugs that slowed the startup time of Windows 7 for some users. Feedback from beta testers is provided passively to Microsoft as telemetry data and Microsoft uses a trace capturing tool running on users' PCs to isolate specific problems. The engineering team now claims it has used that data to reduce slowdown problems with the latest Windows 7 build.

Sinofsky denied in his blog post that 'Microsoft never listens to feedback.' Instead, he suggested that Microsoft takes a scientific approach to dealing with change requests, which helps to avoid mob rule and "adrenaline-based development."

"A key reason we augment our approach with data and studies that deliberately select for representative groups of 'users' is that it is important to avoid 'tyranny of the majority' or 'rule by the crowd'," he explained.

Microsoft has described the general release of Windows 7 as happening in early 2010. However, one source suggested that Microsoft's newest OS could become available as early as the third quarter of this year.

About the Author

Kurt Mackie is senior news producer for 1105 Media's Converge360 group.

comments powered by Disqus

Featured

  • Compare New GitHub Copilot Free Plan for Visual Studio/VS Code to Paid Plans

    The free plan restricts the number of completions, chat requests and access to AI models, being suitable for occasional users and small projects.

  • Diving Deep into .NET MAUI

    Ever since someone figured out that fiddling bits results in source code, developers have sought one codebase for all types of apps on all platforms, with Microsoft's latest attempt to further that effort being .NET MAUI.

  • Copilot AI Boosts Abound in New VS Code v1.96

    Microsoft improved on its new "Copilot Edit" functionality in the latest release of Visual Studio Code, v1.96, its open-source based code editor that has become the most popular in the world according to many surveys.

  • AdaBoost Regression Using C#

    Dr. James McCaffrey from Microsoft Research presents a complete end-to-end demonstration of the AdaBoost.R2 algorithm for regression problems (where the goal is to predict a single numeric value). The implementation follows the original source research paper closely, so you can use it as a guide for customization for specific scenarios.

  • Versioning and Documenting ASP.NET Core Services

    Building an API with ASP.NET Core is only half the job. If your API is going to live more than one release cycle, you're going to need to version it. If you have other people building clients for it, you're going to need to document it.

Subscribe on YouTube