I just finished a round of fun trial and error with our E- 6400's & 4300's, and here's what I found:
Dealing with the Broadcom USH CV devices:
Download the Dell ControlPoint Security Manager Driver from Dell's support website (Thanks Dell for listing the DRIVER in the APPLICATION section!)
Install it on any E-series notebook
Grab the drivers that the install placed in the following folders:
- C:\program Files\dell\Security Device Driver Pack\Microsoft CCID Smartcard Reader
- C:\program Files\dell\Security Device Driver Pack\Dell PBA Device Driver
- C:\program Files\dell\Security Device Driver Pack\Dell Smartcard Keyboard\XP
- C:\program Files\dell\Security Device Driver Pack\Microsoft CCID Smartcard Reader
No filenames are duplicated, so I just combined them all into one new folder in my C:\sysprep\Chipset\ source. (don't forget to update your OemPnPDriversPath in your sysprep.inf!)
The only other device that gave me any trouble was the
Ricoh SD/MMC Host Controller, which Sysprep would always load a default MS driver for a -
SDA Standard Compliant SD Host Controller which Device manager would always end up with a ! on this device.
Strangely enough I got it to work by moving the location for this driver to the very end of my OemPnPDriversPath. Even after double-checking my setupapi.log it had to always be the absolutely last device to load.
For my environment after sysprep completes, I do one-time autologin and call a VBS file for all kinds of scripted fun. I still found it beneficial to install the software components for the Broadcom USH CV devices, but found that the installs would always hang if any new hardware wizard screens were visible. Thats why I bundled the INF's for sysprep to load rather that just rely on the software install alone...
For my graphics chipset I found the Intel provided driver worked best: (Sorry I can't post links yet)
downloadcenter.intel.com/filter_results.aspx?strTypes=all&ProductID=2800&OS FullName=Windows*+XP+Professional&lang=eng&strOSs= 44&submit=Go!
Standard Zip, extract, grab and sysprep injection was a breeze with the 1/24/09 driver release.
Hope this helps someone else!
