This method works just fine for the Broadcom USH device shown above and will work with ‘most’ other devices that show up with missing drivers. One method of locating the driver is to download the driver CAB file (look under the Systems Management section), expand the CAB file and let plug and play figure it out. However, every now and then there may be a driver that you need that is buried in one of the Rxxxxx packs and filed under a category that you would not guess in a million years. Now usually identifying devices on Dell systems is pretty easy since they are pretty good about their driver downloads on their support site.
Dell latitude e6400 support drivers#
I usually make an exception for certain drivers – network drivers being one of them, where I use the drivers provided by the OEM (in this case, Dell).Īfter applying my base Windows 7 image, I see two device bangs – one for Broadcom USH and the other for the ‘Unknown device’: This allows me to keep the driver package as small as possible by using the Microsoft drivers that are included with Windows 7 when possible. One of the first things I do when working on the drivers for a new hardware model is apply the base Windows 7 image without any extra drivers. I usually try to keep driver packages to a minimum since I typically work with customers that have locations spread all over the place, connected by very slow links and no local distribution points (think Nomad). First, let me take a step back and explain the approach I use when it comes to managing device drivers.
On a recent Windows 7 deployment project, I was working on integrating the device drivers for a Dell Latitude E6400 laptop and came across the dreaded ‘unknown device’.
0 kommentar(er)
