Search options (Page 140 of 213)

check my sig for the RAID HWID tool
(HINT since you dont have RAID is just an example - open with 7zip winrar winzip ect... )

yes and no... there is supposed to be a standard... but...

based on wether it reports as a 101, 102, 104, 106, whatever
you should be able to determine the mode... In Theory...

I have played a couple of games that use the emulator... there is actaully a daughter card for PhysX much the same way as the old VooDoo cards...

I say if you need it (and it is unlikely that most of our audience will) you can put it in your own 3rd party DriverPack and every one can get waht they want...   Perhaps ef we asked mr_smartepants real nice he will even make the 3rd party DriverPack for us?

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.

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

" I've tried editing the OEM\DP_Install_Tool.cmd "

well the Tool is not used for a M2 install...
so any changes you make there will be ignored, DP_Install_Tool.cmd is for manually installing drivers (a stand alone driver disc)

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...

give us the HWIDs

to be hence forth and forever known as the "krick" FAQ
oddly enough the kricks of the world will never find it...

http://forum.driverpacks.net/viewtopic. … 746#p23746

for some strange reason i decided NOT to sticky this one

um... wrong forum and no mention of a pack version...

moved to universal imaging

ps excellent info Echo_Platoon !

YES...
now please stop...
read the msfn tut from cover to cover then come back with your IDEAS...
After you have at least a basic working knowledge of the process...

Open driverpacks base select all of your options and instead of hitting the Slipstream button with the mouse do this

hold down the ALT key on your keyboard
you will then notice that the first letter after the "&" sign in the word "&Integrar" is the letter I and it is underlined
as you hold down the ALT key you will also notice there is an underline under the letter S in Sair.
now that you can see the "Hot-Keys" (because they are underlined after you hold the ALT key)
Hit the letter S (while still holding the ALT key down) POOF DriverPacks BASE Exits
Hit the letter I (while still holding the ALT key down) POOF DriverPacks BASE Starts Integrar...ing

Each of the buttons in the language file can (and probably should be) assigned a Hot-Key...
Look at the English language pages with the alt key down

Jeff

PS many of us who have been around longer than the mouse like hot-keys
PSS it is also nice if your mouse is misbehaving

you may have more luck with asking this at UBCD4Win or 911

wae are still working on provideing lan support