Windows becomes the driver operating system

hardware What is a driver?


Whether you're plugging a new device into a USB port, plugging in a headset, or plugging in a new graphics card, the operating system keeps mumbling something like "Driver is being installed," "No driver found," and so on. So it seems like something important!

What does a driver do?

A driver, which is actually referred to as a device driver, ensures that Communicate software with hardware can. In practice, a driver is just a piece of software, often in the form of a single SYS file. Drivers communicate directly with the connected hardware, for example a USB printer, via the bus system, i.e. the cables of a computer. The signals that go to or come from this printer are then processed by the driver in such a way that the operating system can do something with them.

That way there is one on the software side Largely uniform type of access for completely different hardware. It should be logical that a ten-year-old HP printer works completely differently than a current Epson printer. The operating system doesn't really care, thanks to the driver, Windows, for example, can address both equally without Windows itself having to act differently. However, drivers are always written specifically for a specific combination of operating system version (e.g. Windows 7/8/10 x64) and product version (e.g. HP Deskjet F2200). Almost always - but there are also those Generic Drivers.

Generic and complex drivers

If you look on your Windows machine for Driver information you can find them in the Device manager, which you can simply open from the start menu. And here you will probably come across the word "generic", for example with USB devices. And you may have noticed that you can get a driver for the printer from the manufacturer, but not for a USB stick. Under Windows there are device classes such as USB storage devices and sticks developed in compliance with standards can then be addressed via generic drivers intended for entire classes.

This is easy with a USB stick, since the task is limited to transferring data. With a more complex device such as a graphics card, things look different: if you look at the driver details in the device manager, you see that it is not the single SYS file mentioned, but dozens of different files. In addition, you are probably familiar with the software for setting the graphics card, for example the resolution. Regardless of whether it is the Nvidia control panel or the Ati counterpart: they are User interfaces of the drivers. Even mice now have extensive administrative tools.

Now that you know what a driver does, you can quickly explain the common Linux problem that many devices don't run there: Only the manufacturer of a product knows how exactly its hardware needs to be addressed - and he develops his drivers for the only really relevant end-user operating system, Windows. Developing alternative drivers is usually impossible without the help of the provider and not everyone wants to publish their specifications.

Tip: You can only use device functions that the driver makes available - driver updates are therefore always a good idea!