Motorola Mobility, Inc. v. Apple, Inc.

Filing 211

MOTION to Amend/Correct the Procedural Schedule to Serve Supplemental Invalidity Contentions and Accompanying Memorandum of Law in Support by Motorola Mobility, Inc.. Responses due by 1/17/2012 (Attachments: # 1 Affidavit Cathleen Garrigan, # 2 Exhibit A, # 3 Exhibit B, # 4 Exhibit C, # 5 Exhibit D, # 6 Exhibit E, # 7 Exhibit F, # 8 Exhibit G, # 9 Exhibit H, # 10 Exhibit I, # 11 Exhibit J, # 12 Exhibit K, # 13 Exhibit L, # 14 Exhibit M, # 15 Exhibit N)(Mullins, Edward)

The Technical Gm,
to Planning for,
nstalling, Configuring,
Supportm

The Professional's Companion to Windows 95

The Technical Guide
to Planning for,
Installing, Configuring,
and Supporting
Windows 95 in
Your Organization

r soft

indmvs95

Resource Kit

PUBLISHED BY
Microsoft Press
A Division of Microsoft Corporation
One Microsoft Way
Redmond, Washington 98052-6399
Copyright 1995 by Microsoft Corporation
All rights reserved. No part of the contents of this book may be reproduced or transmitted
in any form or by any means without the written permission of the publisher.
Library of Congress Cataloging-in-Publication Data pending.
Printed and bound in the United States of America.
1 2 3 4 5 6 7 8 9 QMQM 0 9 8 7 6 5
Distributed to the book trade in Canada by Macmillan of Canada, a division of Canada Publishing
Corporation.
A CIP catalogue record for this book is available from the British Library.
Microsoft Press books are available through booksellers and distributors worldwide. For further
information about international editions, contact your local Microsoft Corporation office. Or
contact Microsoft Press International directly at fax [phone].
Project Team: Annie Pearson, Emily Warn, Doralee Moynihan, Jane Dow, Audrey Wehba, and

Yong Ok Chung
Project Managers: Steven Guggenheimer and Yusuf Mehdi
Editorial Support and Production: Tony Nahra, Susie Hunter, David Thornbrugh, Bob Bristow,

Dianne Parkin, Brad Matter, and Daniel Tyler
Graphic Design and Production: Sue Wyble, Gwen Gray, Elizabeth Read, Kathy Hall, and

Shane Gonzalez
Technical Contributors: Doug Sheresh, Matthew Bookspan, Kristen Crupi, Joseph Davies,
Pete Delaney, Brent Ethington, Brad Hastings, Jeff Howard, Kris Iverson, Jean Kaiser,
Keith Laepple, Mike Laverty, Phyllis Levy, Rob MacKaughan, Dave Pollon, Adam Taylor,
Christopher Vaughan, and Autumn Womack
Technical Consultants: George Allen, Craig Beilinson, Robert Bennett, Eric Bidstrup, Brian
Boston, Jane Dailey, Harold Daniels, Alec Dun, Micheal Dunn, Tod Edwards, Metin Elyazar,
Brian Emanuels, Wassef Haroun, Ross Heise, Petra Hoffmann, Phil Holden, David Jaffe,
Margaret Jasso, Michael Kammer, Nadine Kano, Steven Lambert, Rhonda Landy, Denise La
Rue, Sarah Lefko, Joo Shian Shirley Leong, Greg Lowney, Roman Lutz, Trang Luyen, Scott
McArthur, Joe Mendel, Brita Meng, George Moore, Gary Natividad, Gale Nelson, Doug Ota,
Kevin Otnes, Ted Padua, Irene Pasternack, Renee Prukop, Jim Reitz, Brian Reynolds, Stephen
Shay, Mark Sundt, Stan Takemoto, Viroon Touranachun, Michael Tuchen, Marianne VanDeVrede,
Keith White, and Robert J. Williams

We are particularly grateful to our most important contributors and reviewers, the Microsoft Windows 95
product development and product support services teams.
continued on page 1349

592

Microsoft Windows 95 Resource Kit

The Windows 95 hardware tree is a record of the current system configuration,
based on the configuration information for all devices in the hardware branch of
the Registry. The hardware tree is created in RAM each time the system is started
or whenever a dynamic change occurs to the system configuration.
Each branch in the tree defines a device node with the following requirements for
configuration:
• Unique identification code, or device ID
• List of required resources, including the resource type (such as IRQ and
memory range) and constraints on specific resources (such as a COM port
that requires IRQ3)
• List of allocated resources
• Indication that the device node is a bus, if applicable (each bus device has
additional device nodes under it in the tree)
• Tip for Viewing the Hardware Tree
Most information in the Windows 95 hardware tree can be seen by using
Device Manager, which you can display by choosing the System option in
Control Panel: Device Manager is described in Chapter 19; "Devices." •
. You can also see the information iii the hardware tree in the
.
„
Hkey_Dyn_Data\Dynamic\Enum section of the Windows 95.Registry.
The configuration process in Windows 95 uses the device nodes to identify
the devices and resource requirements for establishing the working system
configuration. For information about the components that work together in
Windows 95 to configure the system, see Chapter 31, "Windows 95
Architecture."

Plug and Play Support in Windows 95
Plug and Play is an independent set of computer architecture specifications that
hardware manufacturers use to produce computer devices that can be configured
with no user intervention.

Chapter 18 Introduction to System Configuration

593

For Plug and Play-compliant devices, installation consists of plugging in the
device and turning on the computer. For example, a user can do the following:
• Insert and remove Plug and Play-compliant devices such as PCMCIA cards
with automatic configuration.
• Connect to a docking station or network without restarting the computer or
changing configuration parameters.
• Add a new monitor by plugging it in and turning it on.
The Plug and Play capabilities in Windows 95 have been widely described as key
benefits to moving to Windows 95, because of the related reduction in hardware
and software support costs. When Windows 95 detects the presence of a Plug
and Play-compliant device, its device driver can be loaded and configured
dynamically, requiring little or no user input. After the device and driver are
installed, the driver reacts to system messages when a device is inserted or
removed.
Microsoft recommends adding Plug and Play-compliant devices on legacy
computers rather than adding non-Plug and Play devices. To use all Plug and
Play features, however, your system must include a Plug and Play BIOS (the
motherboard), devices (buses), and an operating system (Windows 95).
The following table compares the Plug and Play implementation in the
Windows 95 operating system against other implementations.
Windows 95 Plug and Play

Most other implementations

Dynamically loads, initializes, and unloads
drivers in protected mode.
Supports a wide range of device types
(as described in the following section).
Provides robust detection for devices,
which is critical for Plug and Play on legacy
computers.
Notifies other drivers and applications
when a new device is available for use.
Windows 95 also includes an automatic
installation procedure to ensure that
appropriate drivers are installed and loaded.
Provides robust, seamless operation
through the integration of all subsystems
and the startup process.
Provides an architecture with a consistent
driver and bus interface for all devices.

Run in real mode, with MS-DOS—based
drivers loaded in CONFIG.SYS.
Include only basic PCI-based and ISAbased device configuration.
Do not provide hardware detection.

Configure device IRQ settings and so
on, but the burden of installation falls
on the user.

Might not be as reliable.

In real mode, do not provide a
supporting architecture.

For additional details about the supporting architecture, see Chapter 31,
"Windows 95 Architecture."