the reports are absolutely no help at all...
We do want the packs to be perfect.
You have to help us to help you... that is how it works...
Consider please...
We are not psychic nor are we magicians.
Neither to we have every single hardware device ever sold to test with
(All cataloged and stored individualy in hermeticaly sealed envelopes in the secret DriverPacks environmentaly controled hardware warehouse and archive)
Since we have established that we don't have your hardware 
.
There is no way for us to know the HWID unless you tell us.
Without at LEAST that info we can't even begin to try to fix it.
(needle in a haystack) *problem only exists on your end
You may not be aware that the HWID is the thing the computer actually uses to MATCH a device with its driver
It would be like trying to buy a car part and then telling the parts guy you don't know what kind of a car you have (or the model or year)... . Sorry about your luck. Estimated odds of success, Zero...
To finish the analogy... suppose you took your VIN number off the dash to your parts guy?
you said XP... that narrows it down to about 4096 (possable OS's x Versions x SP levels)
home, pro
oem, retail, corp, Vol,
Service pack levels; none, 1, 2, 3
not to mention slipstreams, SIF files, Etc...
the link in mr_smartepants signature (and in mine) is there for a reason...
If you are unable to provide the clearly itemized list of info, then we can't help you...
so to keep it simple
If you don't have the HWIDs or
If you can't provide DriverPacks BASE and the DriverPacks verisons you used or
If you fail to include the OS and Service Pack version (we do support 2k xp and 2k3 and multiple sp levels for each)
If you fail to include your process (nLite, RVM, Slipstreamed HotFixes or ServicePacks)
if you are unable to test a nightly pack, one that we might belive fixes the issue...
Then you have not been helpful to anyone, not even yourself
Help us to help you!
Provide the requested info. Please.
]]>