[MSDN Library June 1998] Why Use Application Performance Explorer? (100%)

MSDN Library Visual Studio 6.0 > Visual Studio Documentation > Component, Design, and Analysis Tools > Application Performance Explorer Reference > Application Performance Explorer Concepts

[MSDN Library June 1998] Why Use Direct3D Immediate Mode? (26.0209687038955%)

MSDN Library Visual Studio 6.0 > Platform SDK > Graphics and Multimedia Services > DirectX 5 > DirectX Foundation > Direct3D Immediate Mode > Direct3D Immediate Mode: Overview

[MSDN Library June 1998] Why You Don't See Any Disk Data (25.080206012833%)

MSDN Library Visual Studio 6.0 > Windows Resource Kits > Windows NT 3.51 Resource Kit > Windows NT Resource Kit Volume 4: How to Optimize Windows NT > Zen and the Art of Performance Monitoring > Performance Monitor Limitations

[MSDN Library June 1998] Why Performance Monitoring Is Free (Not!) (25.0511700081872%)

MSDN Library Visual Studio 6.0 > Windows Resource Kits > Windows NT 3.51 Resource Kit > Windows NT Resource Kit Volume 4: How to Optimize Windows NT > Detecting Processor Bottlenecks > Analyzing Processor Performance

[MSDN Library June 1998] Why the Processor Queue Is Always Empty (24.470449915272%)

MSDN Library Visual Studio 6.0 > Windows Resource Kits > Windows NT 3.51 Resource Kit > Windows NT Resource Kit Volume 4: How to Optimize Windows NT > Zen and the Art of Performance Monitoring > Performance Monitor Limitations

[MSDN Library September 1992] Why Zero-Length .SBR Files Are Left on the Disk by the PWB (17.3495133966118%)

Knowledge Base and Bug Lists > Programmer's WorkBench KBase

[MSDN Library September 1992] Why Output Might Not Display from VB Form_Load Procedure (17.1602787456446%)

Knowledge Base and Bug Lists > Visual Basic KBase

[MSDN Library September 1992] Why VB Sub Might Stay in Proc: List Even After Code Deleted (16.7365499320853%)

Knowledge Base and Bug Lists > Visual Basic KBase

[MSDN Library September 1992] Why Cooper Software Is Listed in Visual Basic's Copyright (16.4292845935978%)

Knowledge Base and Bug Lists > Visual Basic KBase

[MSDN Library September 1992] Why the First Module in the Code Segment Starts at Offset 16 (15.534262485482%)

Knowledge Base and Bug Lists > C/C++ KBase