Archives for posts with tag: Reliability

Windows 7 is capable of certain levels of self-repair, as you’ve learned. One of the new capabilities in Windows is its ability to recover from serious failures that can impact the OS’s ability to boot. How does Windows 7 handle these errors? Can you boot Windows 7 into Safe Mode or to an earlier functional state when something really bad happens? Yes. You can, depending on the nature of the problem. How?

Stephan Doll, Pavan Kasturi, Desmond Lee and Baskar Sridharan make up most of the team that has enabled Windows 7 to be the most recoverable version of Windows to date. By ensuring that every Windows 7 machine has the ability to automatically diagnose and recover from most boot failures with little or no interaction from the user, this team’s work promises to greatly reduce—or even eliminate—the impact of a serious issue that would otherwise cause significant pain for Windows 7 users.

Tune in.

in reply to Inside Windows 7: Recovering Windows from System Degradation and Boot Failures

I caught up with the great Rico Mariani, Visual Studio’s Chief Software Architect, after his keynote at a VS partner conference held on the Microsoft campus. He tells us all about the improvements in Visual Studio 2010 Beta 2. Rico and team have taken the performance and reliability of Visual Studio to new levels in this release. Gone are the days of synchronous assembly and COM component reference look-ups (woo hoo!!!). Gone are the long start up times. Gone are roughly 90% of the performance bottlenecks that slowed down the development experience inside the VS2010 Beta 1 IDE. The Visual Studio development team worked their tails off to improve perf and reliability across the board. Tune in to learn about what they did and what they will do prior to RTM. Truly excellent engineering goes on in building 42. Well done, team!

Rico also discusses his final blog post in his VS history series, a 5,000 word up to the minute historical piece. After watching Tina’s great VS documentary series, Rico decided to add his own perspective in a 10 part blog post blitz. Great stuff!

Enjoy.

RADAR is a memory leak detection technology built into Windows 7 and integrated with Watson (error reporting) and AutoBug (automatic bug filing). It allows Microsoft product teams and third parties to discover and fix memory leaks early in the product cycle and after release. Since RADAR runs on customer machines, leaks can be caught during public betas, after release, and by third parties, thus ridding the entire ecosystem of memory leaks. RADAR-shipped components are highly optimized to have no appreciable performance impact.
 

Meet RADAR developers Stephan Doll, Baskar Sridharan, Anthony Lorelli‎ and Keshava Subramanya. They dig into the architecture, design and implementation of this great technology. RADAR helps make Windows more reliable and stable by automatically pinpointing memory leaks in code that are then packaged up in bug reports that land in the hands of developers responsible for the memory leaking code. This means quicker to market solutions and knowledge gain that will prevent the same bugs from cropping up again: developers learn what went wrong and why so wthey won’t make the same mistakes again. You’ll learn about the most common mistakes made and you should use this to prevent memory leaks in your own native code.

Tune in. Learn.

Windows Development Manager Melur Raghuraman and team have taken troubleshooting and diagnostics to a whole new level in Windows 7. For one thing, Windows 7 uses managed code “natively” as PowerShell has become the de facto language used for creating diagnostic algorithms that live inside of diagnostic packages. So, when something goes wrong eventually a PowerShell script runs and diagnosis happens.

You’ve probably already noticed the information flag that appears in your task bar notification area when Windows wants to tell you something important. Well, in order for Windows 7 to inform you of a problem and its solution it must first diagnose the issue and collect troubleshooting steps. Sometimes, and more so than ever before, Windows will simply fix the problem and let you know about it – this is a trend that will only become more common over time and with each iteration of Windows going forward. This troubleshooting fabric has both client and server (cloud) components.

How does this all work, exactly? What’s the story?

Tune in. Lots to learn here. The new troubleshooting and diagnostics capabilities in Windows 7 marks a signficant step forward in the evolution of Windows supportability. Of course, you, the human user, can write your own diagnostic scripts – so you’ll be more efficient  when you need to diganosis and then fix some computer problem.

!Analyze is an automatic root cause analysis tool for software failures. For years, it has provided insight to engineers both inside and outside of Microsoft. It is a key enabling technology behind numerous higher-level feedback systems, including Windows Error Reporting and Watson.

!Analyze runs millions of times each day, producing actionable results from reliability telemetry data sent to Microsoft. Ordinary debugging tools report the file and function where a failure ended. !Analyze pinpoints where the failure started.

How does it work, exactly? What’s the story behind !Analyze?

Meet two of the Software Developers behind !Analyze, David Grant and Ryan Kivett. They share with us how !Analyze works, it’s history and provide a glimpse into it’s potential future.Tune in.

Great job, !Analyze team!

PerfTrack is the feedback and monitoring system inside of Windows 7 that performs measurements on, well, all things related to the overall performance of the OS, especially as it relates to system responsiveness to user actions. So, when you click on something (an icon, a folder name, etc…), how long does it take for the user to receive an expected reaction from the system? What are the bottlenecks that lead to a poor experience (user-observable latency) when using some feature in Windows? Is the root problem in the design of the feature itself or with the underlying OS? Enter PerfTrack.

Here, Development Manager David Fields and Group Program Manager Bill Karagounis share their wisdom and experience in the world of OS performance analysis. David and Bill explain how PerfTrack works and we digress into an interesting conversation about power management.

PerfTrack is an example of a technology that provides incredibly important real-world information to Windows engineers that can be used to solve performance problems in Windows.

Enjoy!