Did you remove any drivers with nlite? I had a similar issue where there would be a LONG delay (30+ sec) when connecting USB mouse. But I can't remember what I changed to fix it.
I don't use nlite anymore, so maybe that will fix your issue. I use RVMi removal addons to strip things out now and have my own winnt.sif for unattended options.
Your problem isn't with the USB ports or drivers because your USB ports were obviously working when you set up the systems and before the customers pick up their systems.
I think the problem is with the device manager (or registry) and how XP handles new device detection.
Here's a link to a M$ document on devcon and how to manipulate it from the command line: http://support.microsoft.com/kb/311272
Hope this helps.
2,401 2010-03-15 17:54:34
Re: The 'Found New Hardware' Dialog and USB Keyboards (10 replies, posted in Software)
2,402 2010-03-15 17:35:36
Re: LAN x64 (37 replies, posted in Vista / 7 DriverPack LAN)
Fixed link.
All downloads can be found by clicking the top menu "Downloads" item from the main DriverPacks.net site.
2,403 2010-03-14 05:32:17
Re: [SLVD] Help find XP Sata driver (3 replies, posted in Hardware)
I've read many of the "Read before you post" stuff...
And yet you failed to follow the directions there?!?
Did you even TRY using our DriverPacks? Where's the logs?
You obviously did not read our FAQ or you would have read THIS THREAD!
It took me about 2 seconds to find your drivers by following the link to here.
One Demerit! 
2,404 2010-03-13 19:56:43
Re: Can i get step by step instrunctions on installing driver packs on CD (1 replies, posted in Installation Platforms)
Follow the tutorial linked in my signature.
2,405 2010-03-13 18:25:16
Re: [REQ] Intel Corporation 82801G (2 replies, posted in DriverPack Sound)
The download you point to does NOT contain the HWID you referenced.
Who manufactures the motherboard and what is the model#?
2,406 2010-03-12 17:59:26
Re: [SLVD] Bug HP NC373i & NC373T drivers (74 replies, posted in BartPE - UBCD4Win - WinPE)
Yes, the .inf and .sys are bit-for-bit identical.
Odd that the broadcom .inf files (in \B3, \HP1, and \RIS) are the only ones that have class=net, the other 100+ infs all use the standard class=Net.
And they are the folders that are causing our problems here.
Sounds like a bug in PEbuilder.
I'm still looking, but I don't know if I'll find anything.
2,407 2010-03-11 18:20:10
Re: [SLVD] Bug HP NC373i & NC373T drivers (74 replies, posted in BartPE - UBCD4Win - WinPE)
@Erik see post 35 by cdob
I've already got those.
Arrgh! I feel like I'm playing "Whack-A-Mole"! 
I'm continuing my research into this problem but another user reported (here) that editing the .inf and "changing class=net to class=Net allowed the project to finally add the driver." Seems the \HP1\ drivers are using "class=net". Could that be the problem?
I'll be going through DriverPack LAN again looking for duplicate HWIDs between the broadcom/HP drivers (again). Maybe I missed something.
There are a few duplicates in \B3, \HP1, and \RIS.
Still looking...
2,408 2010-03-11 18:14:03
Re: [SLVD] Dell E6400 sound (19 replies, posted in DriverPack Sound)
Glad to help. That's what we're here for.
You know, with that many workstations, you might be better served with an RIS server to install from. It would sure save time/money on discs! 
Marked as Solved!
2,409 2010-03-10 18:05:49
Re: [SLVD] Trouble with DP_LAN_wnt5_x86-32_1003 (26 replies, posted in BartPE - UBCD4Win - WinPE)
Awesome news! Thanks again cdob for saving the day!
2,410 2010-03-09 18:54:57
Re: [SLVD] Dell E6400 sound (19 replies, posted in DriverPack Sound)
Your system is installing the wrong driver!
You've altered your install source from our recommended settings and it's trying to use c:\drivers\d\s\3st\9\stwrt.inf (not C:\D\S\I9\sthda.inf)
Besides, we don't use the path d\s\3st\ anymore. That path was only in an old nightly build. You must be using an older source and didn't remove the older DriverPack Sound B.
[2010/03/06 20:06:52 608.1212 Driver Install]
#-019 Searching for hardware ID(s): hdaudio\func_01&ven_111d&dev_76b2&subsys_10280233&rev_1003,hdaudio\func_01&ven_111d&dev_76b2&subsys_10280233
#-018 Searching for compatible ID(s): hdaudio\func_01&ven_111d&dev_76b2&rev_1003,hdaudio\func_01&ven_111d&dev_76b2,hdaudio\func_01&ven_111d,hdaudio\func_01
#-199 Executing "C:\WINDOWS\system32\setup.exe" with command line: setup.exe -newsetup -mini
#I393 Modified INF cache "C:\WINDOWS\inf\INFCACHE.1".
#I022 Found "HDAUDIO\FUNC_01&VEN_111D&DEV_76B2" in c:\drivers\d\s\3st\7\sthda.inf; Device: "IDT High Definition Audio CODEC"; Driver: "IDT High Definition Audio CODEC"; Provider: "IDT"; Mfg: "IDT"; Section name: "STHDA".
#I087 Driver node not trusted, rank changed from 0x00002001 to 0x0000e001.
#I023 Actual install section: [STHDA]. Rank: 0x0000e001. Effective driver date: 12/14/2007.
#I022 Found "HDAUDIO\FUNC_01&VEN_111D&DEV_76B2&SUBSYS_10280233" in c:\drivers\d\s\3st\9\stwrt.inf; Device: "IDT High Definition Audio CODEC"; Driver: "IDT High Definition Audio CODEC"; Provider: "IDT"; Mfg: "IDT"; Section name: "STHDA".
#I023 Actual install section: [STHDA.NTx86]. Rank: 0x00000001. Effective driver date: 02/23/2009.
#I022 Found "HDAUDIO\FUNC_01&VEN_111D&DEV_76B2" in c:\drivers\d\s\i7\sthda.inf; Device: "IDT High Definition Audio CODEC"; Driver: "IDT High Definition Audio CODEC"; Provider: "IDT"; Mfg: "IDT"; Section name: "STHDA".
#I087 Driver node not trusted, rank changed from 0x00002001 to 0x0000e001.
#I023 Actual install section: [STHDA]. Rank: 0x0000e001. Effective driver date: 02/27/2008.
#I022 Found "HDAUDIO\FUNC_01&VEN_111D" in c:\drivers\d\s\i7\sthda.inf; Device: "IDT High Definition Audio CODEC"; Driver: "IDT High Definition Audio CODEC"; Provider: "IDT"; Mfg: "IDT"; Section name: "STHDA".
#I087 Driver node not trusted, rank changed from 0x00002002 to 0x0000e002.
#I023 Actual install section: [STHDA]. Rank: 0x0000e002. Effective driver date: 02/27/2008.
#I022 Found "HDAUDIO\FUNC_01&VEN_111D&DEV_76B2&SUBSYS_10280233" in c:\drivers\d\s\i9\sthda.inf; Device: "IDT High Definition Audio CODEC"; Driver: "IDT High Definition Audio CODEC"; Provider: "IDT"; Mfg: "IDT"; Section name: "STHDA".
#I023 Actual install section: [STHDA]. Rank: 0x00000001. Effective driver date: 02/23/2009.
#I022 Found "HDAUDIO\FUNC_01&VEN_111D&DEV_76B2" in c:\drivers\d\s\z2\sthda.inf; Device: "IDT High Definition Audio CODEC"; Driver: "IDT High Definition Audio CODEC"; Provider: "IDT"; Mfg: "IDT"; Section name: "STHDA".
#I087 Driver node not trusted, rank changed from 0x00002001 to 0x0000e001.
#I023 Actual install section: [STHDA]. Rank: 0x0000e001. Effective driver date: 12/14/2007.
#I022 Found "HDAUDIO\FUNC_01&VEN_111D&DEV_76B2" in c:\drivers\d\s\zi\sthda.inf; Device: "IDT High Definition Audio CODEC"; Driver: "IDT High Definition Audio CODEC"; Provider: "IDT"; Mfg: "IDT"; Section name: "STHDA".
#I023 Actual install section: [STHDA]. Rank: 0x00002001. Effective driver date: 12/14/2007.
#I022 Found "HDAUDIO\FUNC_01&VEN_111D" in c:\drivers\d\s\zi\sthda.inf; Device: "IDT High Definition Audio CODEC"; Driver: "IDT High Definition Audio CODEC"; Provider: "IDT"; Mfg: "IDT"; Section name: "STHDA".
#I023 Actual install section: [STHDA]. Rank: 0x00002002. Effective driver date: 12/14/2007.
#-166 Device install function: DIF_SELECTBESTCOMPATDRV.
#I063 Selected driver installs from section [STHDA] in "c:\drivers\d\s\3st\9\stwrt.inf".
#I320 Class GUID of device remains: {4D36E96C-E325-11CE-BFC1-08002BE10318}.
#I060 Set selected driver.
#I058 Selected best compatible driver.
#-124 Doing copy-only install of "HDAUDIO\FUNC_01&VEN_111D&DEV_76B2&SUBSYS_10280233&REV_1003\4&380800DF&0&0001".
#-166 Device install function: DIF_REGISTER_COINSTALLERS.
#I056 Coinstallers registered.
#-166 Device install function: DIF_INSTALLINTERFACES.
#-011 Installing section [STHDA.NTx86.Interfaces] from "c:\drivers\d\s\3st\9\stwrt.inf".
#I054 Interfaces installed.
#-166 Device install function: DIF_INSTALLDEVICE.
#I123 Doing full install of "HDAUDIO\FUNC_01&VEN_111D&DEV_76B2&SUBSYS_10280233&REV_1003\4&380800DF&0&0001".
#-290 Processing REGISTERDLLS section [ST.DLL.RegisterDlls]. Binary: "%11%\stapi32.dll", flags: 0x0001, timeout: 60s.
#E089 Failed to load the OLE Control "C:\WINDOWS\system32\stapi32.dll". Error 127: The specified procedure could not be found.
#E291 Failed to register OLE server "C:\WINDOWS\system32\stapi32.dll". Error 127: The specified procedure could not be found.
#-290 Processing REGISTERDLLS section [ST.DLL.RegisterDlls]. Binary: "%11%\SRSLabs\{176F4E15-8F7C-4833-ADED-81FAE8CCD186}\sluapo32.dll", flags: 0x0001, timeout: 60s.
#E089 Failed to load the OLE Control "C:\WINDOWS\system32\SRSLabs\{176F4E15-8F7C-4833-ADED-81FAE8CCD186}\sluapo32.dll". Error 127: The specified procedure could not be found.
#E291 Failed to register OLE server "C:\WINDOWS\system32\SRSLabs\{176F4E15-8F7C-4833-ADED-81FAE8CCD186}\sluapo32.dll". Error 127: The specified procedure could not be found.
#-290 Processing REGISTERDLLS section [ST.DLL.RegisterDlls]. Binary: "%11%\stcplx.dll", flags: 0x0001, timeout: 60s.
#E089 Failed to load the OLE Control "C:\WINDOWS\system32\stcplx.dll". Error 127: The specified procedure could not be found.
#E291 Failed to register OLE server "C:\WINDOWS\system32\stcplx.dll". Error 127: The specified procedure could not be found.
#-290 Processing REGISTERDLLS section [ST.DLL.RegisterDlls]. Binary: "%11%\stapo.dll", flags: 0x0001, timeout: 60s.
#E089 Failed to load the OLE Control "C:\WINDOWS\system32\stapo.dll". Error 127: The specified procedure could not be found.
#E291 Failed to register OLE server "C:\WINDOWS\system32\stapo.dll". Error 127: The specified procedure could not be found.
#I163 Device not started: Device has problem: 0x0a: CM_PROB_FAILED_START.
#I121 Device install of "HDAUDIO\FUNC_01&VEN_111D&DEV_76B2&SUBSYS_10280233&REV_1003\4&380800DF&0&0001" finished successfully.Please start with a fresh source and try only the current DriverPack Sound B 10.03 integrated with DriverPacks BASE.
2,411 2010-03-09 18:28:10
Re: [SLVD] Trouble with DP_LAN_wnt5_x86-32_1003 (26 replies, posted in BartPE - UBCD4Win - WinPE)
Made your recommended changes to DriverPack LAN 100312. Original .inf backed up to NV\Originals.7z
Uploading now.
Please test the below nightly test dp.
DP_LAN_wnt5_x86-32_100312
http://driverpacks.sytes.net/driverpack … _100312.7z
MD5: d0d90720e429c61c22a10a6a16861a47
Size: 8 MB
v100312
Changed
-NV\ nvnb5032.inf
Commented out 4 HWIDs and added 1.
[Nvidia]
; DisplayName Section DeviceID
;%NVENETFD.DeviceDesc% = NVENETFD1.NDI, PCI\VEN_10DE&DEV_01C3
;%NVENETFD.DeviceDesc% = NVENETFD1.NDI, PCI\VEN_10DE&DEV_0066
;%NVENETFD.DeviceDesc% = NVENETFD3.NDI, PCI\VEN_10DE&DEV_0086
;%NVENETFD.DeviceDesc% = NVENETFD3.NDI, PCI\VEN_10DE&DEV_008C
;Added by DriverPacks
%NVENETFD.DeviceDesc% = NVENETFD3.NDI, PCI\VEN_10DE&DEV_0AB0
v100311
Deleted older conflicting drivers, updated many drivers, added older signed compatible driver (NV2).
New layout for Nvidia LAN drivers.
-NV\ NVIDIA nForce Networking Controller RIS Drivers, DriverVer = 07/11/2007, 67.5.3 & 02/03/2005, 4.7.1
-NV1\ NVIDIA nForce Networking Drivers, DriverVer = 04/06/2005, 4.8.2
-NV2\ NVIDIA nForce Networking Drivers, DriverVer = 05/15/2006, 60.1.5
-NV3\ NVIDIA nForce Networking Drivers, DriverVer = 03/06/2007, 65.6.5
-NV4\ NVIDIA nForce Networking Drivers, DriverVer = 09/20/2007, 67.6.4
-NV5\ NVIDIA nForce Networking Drivers, DriverVer = 08/01/2008, 67.8.9
-NV6\ NVIDIA nForce Networking Drivers, DriverVer = 07/01/2009, 71.0.8
-NV7\ NVIDIA nForce Networking Drivers, DriverVer = 07/01/2009, 73.1.0
Restored signed driver .inf where possible. \NV4 is still not signed (unknown source).
Added BartPE code to .ini. All NV* folders are skipped for wxp, w2k3 sources. NV\ RIS drivers are preferred at the moment for BartPE (requires testing).2,412 2010-03-09 18:13:53
Re: Graphics DriverPacks are final! (37 replies, posted in News)
Updated changelog info on official download links with above info. 
Thank you for your suggestion to make DriverPacks better!
2,413 2010-03-09 02:21:32
Re: [SLVD] Trouble with DP_LAN_wnt5_x86-32_1003 (26 replies, posted in BartPE - UBCD4Win - WinPE)
Please test the below nightly test dp.
DP_LAN_wnt5_x86-32_100311
http://driverpacks.sytes.net/driverpack … _100311.7z
MD5: 37703ac4f5349328f9b1e60539decf2c
Size: 8 MB
v100311
Deleted older conflicting drivers, updated many drivers, added older signed compatible driver (NV2).
New layout for Nvidia LAN drivers.
-NV\ NVIDIA nForce Networking Controller RIS Drivers, DriverVer = 07/11/2007, 67.5.3 & 02/03/2005, 4.7.1
-NV1\ NVIDIA nForce Networking Drivers, DriverVer = 04/06/2005, 4.8.2
-NV2\ NVIDIA nForce Networking Drivers, DriverVer = 05/15/2006, 60.1.5
-NV3\ NVIDIA nForce Networking Drivers, DriverVer = 03/06/2007, 65.6.5
-NV4\ NVIDIA nForce Networking Drivers, DriverVer = 09/20/2007, 67.6.4
-NV5\ NVIDIA nForce Networking Drivers, DriverVer = 08/01/2008, 67.8.9
-NV6\ NVIDIA nForce Networking Drivers, DriverVer = 07/01/2009, 71.0.8
-NV7\ NVIDIA nForce Networking Drivers, DriverVer = 07/01/2009, 73.1.0
Restored signed driver .inf where possible. \NV4 is still not signed (unknown source).
Added BartPE code to .ini. All NV* folders are skipped for wxp, w2k3 sources. NV\ RIS drivers are preferred at the moment for BartPE (requires testing).2,414 2010-03-09 01:19:15
Topic: Where can I find drivers for my hardware? (0 replies, posted in Frequently Asked Questions)
If you insist on asking this question in the forums, you will be referred to this thread.
1) If you tried using the DriverPacks by integrating with DriverPacks BASE and your device still does not work after Windows install, then proceed to next step.
2) Get the HWIDs for the device with no driver, use our HWID tool.
3) Search for the vendor and device (VEN_xxxx&DEV_yyyy) by using Google. Try to find a good driver from the vendor themselves.
4) When all else fails, look for a compatible driver using the driver index here: http://www.downloadwindowsdrivers.info/
- Example:
- Searching for PCI\VEN_10DE&DEV_0389
- Try http://www.downloadwindowsdrivers.info/ … /dev_0389/
If and ONLY if you can't find a driver this way, THEN ask for help.
Read the Read before you post thread, then post the info that we have requested (HWIDs, logs, etc.)
Remember that the DriverPacks team spends hundreds of man-hours building and testing these DriverPacks FOR FREE so that you don't have to. Please do us the courtesy of performing a little research before asking for help.
2,415 2010-03-08 23:25:18
Re: [SLVD] Trouble with DP_LAN_wnt5_x86-32_1003 (26 replies, posted in BartPE - UBCD4Win - WinPE)
I'm rebuilding all the NV* folders in DriverPack LAN from scratch. There were so many altered .inf files it was difficult to find the original ones.
This will take me most of today to do (my only day off!).
I'm also updating some of the folders with newer drivers, and pruning duplicate folders/drivers.
Jaak had done an amazing amount of homework regarding the nvidia LAN drivers here: http://forum.driverpacks.net/viewtopic.php?id=2752
It's worth a read (I've read it 3 times just this morning!)
I've got a pot full of coffee and no distractions for the next two hours...
Hopefully I'll have a working DriverPack LAN nightly for you guys to test by the end of the day.
2,416 2010-03-08 21:38:40
Re: [IMPL]NVNET_DEV0268 - please add it to the official driverpacks (5 replies, posted in DriverPack LAN)
I have altered \NV7 to restore the signed .inf and provided a new DriverPacks.inf for this HWID. That should solve a few issues!
New nightly is still in work though. Nothing for anyone to test at the moment.
2,417 2010-03-08 21:36:12
Re: PCI-modem driver for Fujitsu Siemens Scaleo (4 replies, posted in DriverPack LAN)
Please read this FAQ
Did you follow the tutorial for DriverPacks BASE?
Please post your log files as I requested in your other thread.
2,418 2010-03-08 20:51:30
Re: Looking for Ethernet driver to Fujitsu Siemens Scaleo D1627 (1 replies, posted in DriverPack LAN)
Too hard? There is only one DriverPack LAN! 
Please read this FAQ
Please post your logs as listed in the "read before you post" linked in my signature.
2,419 2010-03-08 19:25:07
Re: Graphics DriverPacks are final! (37 replies, posted in News)
3rd Party DriverPacks addons for Graphics
Place the following DriverPacks in \DPs_BASE\3rd party DriverPacks\ directory
Does that sound better?
I for one ONLY include the PhysX Third Party DriverPack, but that's because I only do English-only installs and I use my own .NET installers.
As a better explanation:
DP_Graphics_Languages_wnt5_x86-32_*
By default, the DriverPacks are mostly English-only. Adding this Third Party DriverPack will add every language and locale to the individual driver folders when used in conjunction with DriverPack Graphics A & B & C.
DP_Graphics_PhysX_wnt5_x86-32_*
Makes the Nvidia PhysX installer available to the Nvidia drivers. If applicable, the Nvidia drivers will install PhysX between T-35 & T-33 of Windows XP setup.
DP_Runtimes_wnt5_x86-32_*
*
Installation is handled by DriverPacks Finisher (either GUIRunOnce or RunOnceEx depending on your DriverPacks BASE settings) and are scripted to execute prior to ATICCC being installed, if applicable. Will not install if ATI card is not present during XP setup.
2,420 2010-03-07 02:49:51
Re: [SLVD] Trouble with DP_LAN_wnt5_x86-32_1003 (26 replies, posted in BartPE - UBCD4Win - WinPE)
Overflow is concentrating on finishing the code for DriverPacks BASE. I will look into this problem further but now that cdob is here hopefully we'll find a solution soon.
I have very little experience using BartPE. I built my first UBCD4win disc last week!
2,421 2010-03-06 20:31:54
Topic: Nvidia 196.75 Drivers pulled due to potential hardware damage. (0 replies, posted in News)
WARNING! Nvidia 196.75 drivers pulled due to hardware damage!
**Update**
Nvidia has released 197.13 WHQL drivers that resolves the fan-speed bug.
As a reminder, we at DriverPacks.net do NOT include beta or testing drivers in our release DriverPacks.
NVIDIA is aware that some customers have reported fan speed issues after installing 196.75 drivers from NVIDIA's website. These drivers have been removed from NVIDIA's website due to these customer reports. We have also asked all partners to remove this driver. We recommend that all customers immediately discontinue the use of 196.75 drivers and roll back to their previous driver. Driver roll back help can be found here. For those that have experienced fan speed issues with 196.75 drivers, NVIDIA has setup this feedback site
This problem does NOT affect the current DriverPacks. However, development of the Graphics nightly test packs has halted on the recent news from Nvidia.
I want to reassure our users that NONE of the current DriverPacks contain any of these faulty drivers from Nvidia.
However, if you have upgraded any of your systems to use the Nvidia 196.75 drivers for any GeForce/ION/Quadro platforms, please uninstall those drivers immediately and revert to an older driver for your respective hardware until an appropriate fix can be made.
Please make any replies to the Official Nvidia forum thread: http://forums.nvidia.com/index.php?showtopic=161503
Or to this Nvidia feedback site
2,422 2010-03-06 18:25:39
Re: [SLVD] Trouble with DP_LAN_wnt5_x86-32_1003 (26 replies, posted in BartPE - UBCD4Win - WinPE)
SamLab had made some edits to the NV*\ .inf files to fix some HWID overlap bugs. I haven't compared DriverPack LAN 8121 with 1003 yet in that regard but I'll bet there are changes.
I have the nvidia 15.26 nforce drivers for your board with me. I'll try to have another look. Maybe SamLab's changes broke something?
2,423 2010-03-05 21:24:23
Re: New releases for March 2010 (2 replies, posted in News)
Uploaded DriverPack Sound A & B.
It only took two years...
2,424 2010-03-03 18:20:43
Re: [SLVD] Trouble with DP_LAN_wnt5_x86-32_1003 (26 replies, posted in BartPE - UBCD4Win - WinPE)
Well, that HWID has a duplicate in DriverPack LAN. Both \NV\ (07/11/2007, 67.5.3) and \NV8\ (10/12/2007, 67.6.7) have that HWID.
In fact, looking at the nvidia website, your board should be using the following versions:
# Ethernet Driver (v67.89) WHQL
# Network Management Tools (v67.96) "Sedona"
Maybe that's the problem? Maybe I need to add some BartPE exceptions to the pack .ini.
Can you delete the \NV\ folder from the pack, rebuild your BartPE plugin and try again?
2,425 2010-03-03 18:08:36
Re: [SLVD] Dell E6400 sound (19 replies, posted in DriverPack Sound)
Let me know what you find Major, I'm finalizing both sound DriverPacks now for a weekend release.
I'll try to look into this as well but I'm swamped.