Well, you do not request additions to the 3rd party DriverPack, at least usually.
Instead, you add them yourself and share with the rest of us. Give and take so to speak.
How can I add them myself? I haven't write access to the 3rd Party DriverPacks folder.
Ususally, any request is accepted if the driver is really not present already AND it is common HW (so no specifically, just made-for-you stuff).
A nice description of the device, HWIDs, the versions of the DriverPacks you already included that did not support it, maybe some log files, a proper link to the official non-beta driver hosted on the manufacturer's webspace and a polite post ususally greatly enhance your chances of acceptance, though
Quite reasonable. I modified all my requests accordingly. Maybe someone should write a sticky post on "how to make drivers requests"
Other than that, you are of course always free to create your own personal 3rd party DriverPack (you dojn't even have to share it if you do not want to).
I do prefer to share: I hate to think that the time I wasted to solve a problem might be wasted by someone else who has the same problem.
Regarding creating my own pack, most of the times I manage to add drivers to my own pack following this nice tutorial, but sometimes I feel lost when the tutorial rules don't apply to the drivers I am dealing with. For example, I have these files of a driver which don't include an .inf file:
AUTORUN.INF
Autoswitch.exe
data1.cab
data1.hdr
dir.txt
dot.bmp
engine32.cab
Install.ini
Install6x.dll
KILLW16.EXE
layout.bin
setup.exe
setup.ibt
setup.ini
setup.inx
setup.isn
SMSetup.exe
Thumbs.db
VSSVER.SCC
The AUTORUN.INF contains only:
[Autorun]
Open=Autoswitch.exe
icon=setup.exe
label=Adapters
