Similar device on ProBook 6455b running XP. Using driver pack WLAN 11.01


Device shows a yellow circle with an exclamation mark in device manager.

Had to install this driver instead: … ob-83744-1

D\3\MON\IBM\l197wide.inf references "L197" and "L197 Wide.ICM" but the actual files included with the pack are called "" and "l197wide.icm"

Seems like this should be corrected by either renaming the files or by changing the names in the .inf file.

In my testing, dp_inst_tool was not even needed. Devpath alone was sufficient for Mini-Setup with UpdateInstalledDrivers=Yes and DriverSigningPolicy=Ignore. It was not necessary to select Detect Non-plug and play hardware. That extra step just took more time and made no difference.

Yes, wifi was enabled during install. These laptops don't have a physical switch but they do have a Fn key for turning wifi on and off. Let me know if there is anything I can do to help.

I'm having issues with the driver for a Synaptics touchpad on an HP ProBook 4420s.


The buttons are part of the touchpad similar to newer apple laptops. This causes the pointer to jump around when a finger is resting on the button.

This issue is somewhat improved by installing the following driver: … ob-86824-1

Would it be possible for this driver for the LSI HDA Modem to be added? … ob-80688-1


Thanks for the response. The machine is an HP ProBook 4420s.

The following driver works: … ob-83730-1

I was incorrect. Vendor and Device IDs are the same but subsys is different. Not sure if that matters or not.


This is an extension to my above post. Here are the remaining issues I'd like to solve:

Sometimes on the first boot of Windows, the New Hardware Wizard will appear and wait for me to click next before continuing to install drivers automatically.

It appears to be related to driver signing. I tried setting driver signing to ignore, but it seemed to have no effect.

The next issue is related to the one above.

Certain machines do not have PS/2 ports. Often USB keyboards and mice do not work on the first boot after imaging. I can't click next on the new hardware wizard so it just hangs the entire process at that point.

A solution I'm considering is using sysprep with the pnp option to re-detect all the hardware on the first boot.

Any advice would be appreciated.

Thank you Phyxx and everyone for this very helpful thread. I'm planning to use a modified version of this method to re-image a large number of machines in our organization.

I'd like to provide my version of this process here. This has not been rolled out into production yet, so please point out any errors or potential issues that we may encounter. I'm still working on fully testing this process.

I chose to build my base image in a virtual machine. We are running XP SP3.

After downloading all the XP driver packs and a few third party ones, I extracted them all into a single D folder which I placed on a network share.

Acronis Universal Restore can automatically search a network location for drivers. I found that UR is very effective when given such a large library of drivers to pull from. As stated earlier in this thread, UR can't access cab compressed drivers.

By using the network share, and uncompressed drivers, I found that Phyxx's method of manually referencing a Vendor and Device ID table was completely unnecessary. UR found all the drivers it needed automatically.

This eliminated the problem of machines that BSOD on first boot after being imaged. UR replaces the HAL, Mass Storage, and other files that are critical for boot.

Unfortunately, this only solves half the problem. AR is very good at getting systems to boot successfully, but after that, there is still a large number of drivers missing.

I placed a copy of the D folder on the C:\ drive of my image. I used Phyxx's InfLocator tool to scan the folder tree and create the appropriate registry key.

The combination of these two things allows me to create nearly universal images.  AR gets the system booting, and Windows handles the remaining drivers thanks to the driver packs.

chumbo wrote:

Here you go.


I wonder why the card isn't recognized by the newer driver.  I'll have to try to load it manually and see if it's there.

Same issue here in the XP driver packs version 10.09.  Same hardware IDs as posted above. The card is based on the Atheros 9285 chipset.

Just wanted to say that I've also experienced this issue.  Thanks to this thread, I was able to work around it by not using the cab compressed versions of the files.