Learn the terms behind the procedures: driver roles, execution modes, request stacks, signatures and device status messages. The articles explain these…
What this section covers
Learn the terms behind the procedures: driver roles, execution modes, request stacks, signatures and device status messages. The articles explain these ideas without treating them as diagnoses. Understanding a term can help you read a system report, but it does not prove which component caused a symptom.
Applications rarely talk to hardware directly. They ask the operating system, which passes the request to the driver for that device; the driver translates it into commands the hardware understands.
Knowing these layers helps make sense of symptoms. A problem in one application suggests a different layer from a problem that affects every program using the same device.
The layers this section covers
1Applicationasks for work
2Operating systemroutes the request
3Drivertranslates it
4Firmwareruns on the device
5Hardwaredoes the work
A simplified model; each Learn page explains one layer and how it hands work to the next.
Key terms
Words worth knowing early
These terms come up throughout the library; the glossary has fuller definitions.
Driver: software that lets the operating system use a device
Firmware: software stored on and run by the device itself
Driver signing: a check that a driver package has not been altered
Hardware ID: the identifier a device reports to the operating system
Concept
What a driver does, in one picture
A program never talks to hardware directly. Each request is handed down a chain, and the reply comes back the same way.
1Applicationasks to print, play or read
2Operating systemturns it into a standard request
3Drivertranslates it for this hardware
4Devicedoes the work and replies
Requests travel down from the application to the device; status and data travel back up. When something fails, the layer that failed usually leaves a visible status.
Follow one request through the layers
An application asks for an operation through operating-system interfaces. One or more driver components may translate, filter or route that request before hardware performs work. Some components never communicate directly with hardware. The diagram and reading below simplify that path deliberately; actual device stacks vary, and a drawing is not a live view of your computer.
We use essential storage to remember this choice. Optional analytics and advertising categories stay off unless you turn them on, and no optional tags are loaded at this time.
Your browser sent a Global Privacy Control signal, so optional categories stay off whatever you choose here.