You are not logged in. Please login or register.
Hi, I am new here and to driverpacks. I have several questions.
Driverpacks didn't have some of my hardware models in the list, what can i do?
I Don't think driverpacks support vista?
What about other drivers like printers and fingerprint reader, how can i intergate those drivers into my vista setup DVD? It's MSI and EXE extension not .info therefore i cann't use nlite to intergate those.
Thank you for your support
Last edited by onetime (2008-03-03 06:28:17)
Welcome to DriverPacks, thanks for joining.
sorry, we haven't added support for vista yet.
What about other drivers like printers and fingerprint reader, how can i intergate those drivers into my vista setup DVD? It's MSI and EXE extension not .info therefore i cann't use nlite to intergate those.
You will need to extract these first, so that you can obtain the .INF and .SYS files that vlite will need.
This can mostly be done with 7-Zip, but Universal Extractor is a safe bet, too.
Besides, since when does nLite work with Vista and what are those .INFO files you are talking about?
Greetings. Thanks for your work. I use DriverPacks since 2007. Last versions, at unpacking, create a one separate folder in folder D. So was and earlier. However, DP_WLAN_wnt5_x86-32_802 at unpacking, creates 208 folders in folder D. Whether it is correct? Thanks.
Last edited by Valueff (2008-03-30 07:33:53)
Hi
we did that to get a shorter path in method 1
Wlan: ;D\W\B\1; is longer than ;D\WB1; (notice that all Wlan drivers start with letter W)
approx 200 * 2 + removal of 70 folders... that shortened the path a good deal.
Lan ; D\L\B\1 is longer than D\LB1 (all Lan drivers can start with letter L. We have a testpack like that.)
we may go back to longer path.. Method 1 is seldom used, and those that want a Method 1 DVD with short path CAN edit the slipstreamed source.. I currently do this to get from 4500 (which used to be approx 7000) to under 4000 (with all packs streamed)
to make that viable with the finisher i will have to edit the base to point to the D\Wxx folders
the finisher and KTD will expect the old subfolders until i add the new folders to the list
this will be most evident for the split packs like sound and video
Hi Jeff
when I went ahead with Wlan, we was unaware of that issue with KTD..
I should upload a "standard" WLAN asap.
Which I did..
WLAN again uses "standard" subfolders under D\W\
I think that it is important to note that KTD; All, paths, and patterns will be unaffected
it only effects KTD if useing custom "pack" selection and when not all packs are selected
for the most part only sound and graphics will have issues (the split packs)
or other packs if KTD is NOT set to ALL and if folders are shortned to \D\*.*
again the workaround is to specify your KTD manually useing the "paths" method
Besides, since when does nLite work with Vista and what are those .INFO files you are talking about?
oops, i meant vlite. I got another question, What about driver signing thingy? does nlite ignores that yet with its latest release cause I have heard that only drivers that are signed are able to integrate. They said that most of the drivers from manufactures are signed and thus able to integrate with nlite. Drivers from intel and nvidia website are signed don't they?
You can disable the Singed Driver's Policy in nLite - that's what I recommend to do regardless of whether you use unsigned ones or not.
Thing is, if you happen to use a non-signed one unknowingly, XP will pick the signed one over it even if that turns out to be (much) older.
Probably not what you'd want if you already make the effort to integrate them.
Personally, I see little gain in having XP not installing unsigned drivers automatically - well, as long as you know what you're doing anyhow.
A signed driver does NOT mean it's bug-free or anything.
It can still cause your system to BSOD so it guarantees you little.
While most drivers are indeed signed, editing the INF file or leaving the CAT behind will break WHQL certification.
As long as you stick to the latest official (non-beta) drivers you should be fine in most cases, WHQL or not 
Powered by PunBB, supported by Informer Technologies, Inc.
Currently installed 3 official extensions. Copyright © 2003–2009 PunBB.
[ Generated in 0.024 seconds, 10 queries executed ]
