Re: I remember @AC
The way that Windows device driver identification works is fundamentally broken IMHO.
It requires you to have a specific driver for the USB and PCI (and I presume PCIe) device identity. This is normally provided by the manufacturer (remember all those shiny round things that came with the device).
The result is that if you upgrade a windows system, and the existing propriety driver that used to work fails the upgrade compatibility check and is removed from the configuration, the device will be left with no driver loaded. This is even if there are perfectly good drivers for that particular device on the system (this is particularly bad for network devices that are largely built from standard chipsets).
in the case of network drivers, this may mean that you can't even get to the Internet to try to find working drivers!
The Linux model, which has generic drivers for almost all of the chipsets included with the OS, and a device ID mapping file that points to the correct generic driver for a particular device, means that as long as you can identify what driver should be used, even if it is not in the config. file already, you have a fighting chance of getting it working without having to find another machine and start mucking about with USB memory sticks to copy the driver to re-install.
And you're not beholden to a device manufacture who has no real interest in providing new drivers for old hardware.