Search options

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.

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

ACPI\SYN0168

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:
http://h20000.www2.hp.com/bizsupport/Te … ob-86824-1

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

The following driver works:
http://h20000.www2.hp.com/bizsupport/Te … ob-83730-1

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

PCI\VEN_168C&DEV_002B&SUBSYS_3040103C&REV_01
PCI\VEN_168C&DEV_002B&SUBSYS_3040103C
PCI\VEN_168C&DEV_002B&CC_028000
PCI\VEN_168C&DEV_002B&CC_0280

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.