![]() |
| |||||||
| Notices |
![]() |
| LinkBack | Thread Tools | Display Modes |
| | #1 (permalink) |
| We're shipping XPe based product and one of our customers wants to put a couple of our devices on a KVM that uses a USB mouse and keyboard. When plugging in the KVM, the hardware is discovered but the Hardware Update Wizard fails. When I tried it here, I tried pointing the Hardware Update Wizard at the i386 folder on an XPPro disc, but to no avail. It looks like I can add the needed drivers to new images with the "Generic USB Input Device Support" component, but that doesn't help for the devices already in the customer's hands. So my question is: what's the best way to install XP drivers after the image is in the field? As mentioned previously, I tried just using an XPPro CD, but that didn't work. | Guest
Posts: n/a
|
|
| | #2 (permalink) | |
| s.k.easley, If you are talking about PnP devices, the easiest way to add those to the image running in field is to copy driver related files to appropriate windows directories (\windows\inf, \windows\system32, \windows\system32\drivers). Also, please make sure the original image includes required Class Installer and CoInstall components and "USB Composite Device" component (often required by a switch to work). It would be interesting to know why the Hardware Wizard failed for you (assuming the install you pointed it to included missing drivers). You or your customers can analyze \windows\setupapi.log file to get more details. -- ========= Regards, KM Quote:
| Guest
Posts: n/a
| |
|
| | #3 (permalink) | ||||
| Thanks KM, I think you're right that 'USB Composite Device' needs to be in the original image, but that doesn't help me fix the units that are already in customers hands. I got pulled onto another project, but now I'm back and I'm going to start working this problem again. I'll post what I find. On Dec 28 2006, 5:51 pm, "KM" <konstmor@nospam_yahoo.com> wrote: Quote:
| Guest
Posts: n/a
| ||||
|
| | #4 (permalink) | ||||||
| s.k.easley, Quote:
You can always add those component manually at run time. Beside the bianries corresponding registry entries need to be grabbed from components on XP Pro, or you can use devcon to install related INFs. -- ========= Regards, KM Quote:
| Guest
Posts: n/a
| ||||||
|
![]() |
| Tags |
| None |
| Thread Tools | |
| Display Modes | |
| |
| ||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Post-FBA installation of .NET 1.1, .NET 1.1 SP1, and .NET2.0 | archilea@gmail.com | Windows XP Embedded | 0 | 12-06-2006 01:58 PM |
| Windows Vista last release installation | Alberto | Windows Vista Install & Setup | 4 | 10-12-2006 10:35 PM |
| Final Release Installation Question | Ben | Windows Vista Install & Setup | 4 | 10-04-2006 09:03 PM |
| Release of an AODV Driver for Windows XP | Asanga Udugama | Windows XP Device Drivers | 0 | 08-27-2004 03:52 PM |
| IEEE 1394b Driver Release Date | Gerald | Windows XP Device Drivers | 0 | 05-28-2004 09:41 AM |