[HOWTO] Using DriverPacks w/ Sysprep (Updated for BASE 7.04) (Page 4 of 9)

If i were going to guess it would be drivers that are upgrade/replacements for existing windows drivers.

by adding the driverpack you create HWID duplication with native drivers... just a guess.

PS easy test to find out run your hwids list against txtsetup.sif...

DP BartPE Tutorial   DP_BASE Tutorial   HWID's Tool     Read BEFORE you post    UserBars!

The DriverPacks, the DP_Base program, and Support Forum are FREE!.

If you use nLite and also plan to use the DriverPacks, for the sake of simplicity, universal HW support and your own sanity, please do keep all original Windows drivers!

It is kind of pointless wanting to remove loads of drivers fro your disc, then use nLite to add loads of drivers again, while none of these are overlapping.
The point of the DriverPacks was to support as much HW as possible, hence it was made with the idea in mind not to include drivers that are already present on the Windows disc, as a user who'd want to add most comprehensive HW support would not remove those.

Coming up next - useful links:
• If you like this project, please support it with your donation!      • Grab your HW info (HWIDs) here!     
• If you are a newbie, be sure to check out the DriverPacks tutorial!     • Here's how to create your own DP!

should I specify the KTD location as %SystemDrive%\D instead of the default?   NO...!
NEVER SET THE KTD LOCATION TO DriverPacks ROOT (%SystemDrive%\D)

your best option is probably to integrate mass with one of the recomended methos here (for sysprep) and not call the finisher when you do your install (finisher = custom) in this way the drivers are available until needed (target machine) then run the finisher on the target... this does add 1.5 gig to the copy... but it will be deleted right after the deployment. it is not feasable to do this any other way... (what would happen if the LAN driverwere being updated from a network location... boom... same for chipset... there is no way around keeping the drivers local until after deployment. forget about the size and keep your eyes on the prize... a UNIVERSAL image...
Stay on target, you can have small or universal not both... if you want small then use one image per machine...

you might also use the SAD Disc method for driver install instead of the method you are following.
integrate mass per sysprep...
copy a SAD disc (M2) to your image and call it on first boot. in this way the copy is only the 300MB for the compressed packs instead of the 1.5 gig of extracted drivers

DP BartPE Tutorial   DP_BASE Tutorial   HWID's Tool     Read BEFORE you post    UserBars!

The DriverPacks, the DP_Base program, and Support Forum are FREE!.

you dont want or need KTD...

you need to integrate mass storage useing syprep (yes just mass storage)

then you can either
use the driverpacks M2 without the call to the finisher. this will leave the \D\ folder and all the finisher files in the root of the drive, and the \D\ folder should already be in the PnP search path (i am not sure if this registry value is cleared with sysprep - but if it is you could just call devpath to repopulate it then when the image is deployed the drivers are used teh finisher is run and the DriverPacks are removed (same as a normal install)

or you can use the SAD Disk option - just run the stand alone driver install after deployment... and then delete it.

DP BartPE Tutorial   DP_BASE Tutorial   HWID's Tool     Read BEFORE you post    UserBars!

The DriverPacks, the DP_Base program, and Support Forum are FREE!.

v2.4 of FindHWIDS is out. It get's rid of a couple false HWIDS that popped up. You should get clean HWIDS now.

In this topic I aked for powerful filtering of duplicates.
I found out excel 2007 has powerful sort functions.

I found a powerful suite of excel add-ins (Sorry, not free.)
http://www.office-excel.com/excel-addin … undle.html

I found out that nothing one can automise will handle all permutaions, and the human should have the last decision, because of GiGo.
Garbage IN (what one uses as source of scanned file for output.)
Garbage OUT (what one can get if the developer does not corroberate findings to other findings.)

is anbody who is not on the testing team interested in testing the new SysPrep Platform?
I added support in the unreleased (publicly) alpha version, but, if anyone is interested...

DP BartPE Tutorial   DP_BASE Tutorial   HWID's Tool     Read BEFORE you post    UserBars!

The DriverPacks, the DP_Base program, and Support Forum are FREE!.

*raises hand*
I'd love to have a look at this
Cheers

Regarding the guide in the first post, if it's ok to post questions/comments in this thread, could you indicate exactly what KTD is? I thought it was Keep The Drivers but maybe an explanation would be better for someone who doesn't browse the site/forums. Also, I'm trying to do what many are doing by building a sysprep image that includes chipset, lan, and mass storage drivers. The guide says that as of writing the include method mentioned therein didn't work for the mass storage package at the time. Does it still not work with the current package? I would guess no since I'm trying to build a model image via VMWare and got the "Error updating registry" error when (presumably) trying to include that package. What do the admins. here recommend as the best solution for including in addition the mass storage drivers for a sysprep image? This model image needs to work across many different age and type machines, from dual core AMDs to P4s and with all types of MBs and drives. HAL switching is done with UpdateHAL=ACPI APIC_MP,%windir%\inf\hal.inf and has so far worked, but I'm running into machines with newer hardware and thought of including these packs for ultimate compatibility.

@EvilBetty... Done.

@chipzoller

KTD = Keep The Driver
An out dated method of making drivers available on the machine permanently.
This currently requires over two gig of disk space for drivers that probably will never be used.
And if they were used then they would be out of date.
KTD has been made obsolite by our SAD (Stand Alone Driver) platform

We are still working on a solution for SysPrep... ATM OffLine SysPrep by Galapo is your best option (yes he uses the DriverPacks)...

DP BartPE Tutorial   DP_BASE Tutorial   HWID's Tool     Read BEFORE you post    UserBars!

The DriverPacks, the DP_Base program, and Support Forum are FREE!.

I might have done

Local $a[3] = "Hardware Installation", "Confirm File Replace", "Installation Complete"
Local $b[3] = "C", "{TAB}{TAB}{ENTER}", "{ENTER}"

do
sleep (250)
For $i=1 to 3
If winExists($a[$i]) then WinActivate($a[$i]) if WinActive($a[$i]) then send($b[$i])
Next
Until "we're"=="done"

DP BartPE Tutorial   DP_BASE Tutorial   HWID's Tool     Read BEFORE you post    UserBars!

The DriverPacks, the DP_Base program, and Support Forum are FREE!.