Search options (Page 85 of 213)

we do not accept drivers from rapidshare or the like... only links to OEM sources...

I am pretty sure those are included... please provide your HWID's so we can see.

it may be to your advantage to copy the inf files from the \D\C\I1 folder (possably others) into your target machines INF folder

IE seed the chipset drivers you will be useing

It is and it is not...

One of our Users started on an idea... what if we only extract the drivers we need instead of all of them? Would it be faster? Better? He started coding... and did well, eventually convincing me that it was worth while. I then challenged them to a race LOL. I took the ball and ran with it... In the process I accidentally fixed a bug in one of the HWID's tools that we use to update the packs . Now that it is working in beta form I see that it will have other uses other than it's original intent. IE We have had requests for Per Machine packs. This is not feasable for us... However a user could use this tool to generate thier own per machine pack... which is a cool side effect.

The result is much like SAD M2,
except it only extracts drivers that match the HWIDs of the target machine... 
(warmsnows app will also do this...)

Did i mention this tool is BETA or what we call a 'nightly'...
the finisher is not called from the script
this allows you to see what was extracted / got matched with the machine
the finisher can be run manually

I hope that helps

that mass controller is a standard windows driver... you should not need to add anything for that to be detected

the DriverPacks do not include drivers that are shipped with windows... if you used nLite or similar program to remove the native windows drivers then you shot yourself in the foot...

I must correct myself... That / those driver/s is/are in DriverPack MassStorage 9.01

[AM1]
ms_count=1 
ms_1_deviceName="AMD PCI SATA/IDE"   
ms_1_tag="amdide1"   
ms_1_sysFile="amdide.sys"   
ms_1_hwids="PCI\VEN_1002&DEV_4390,PCI\VEN_1002&DEV_439C,PCI\VEN_1002&DEV_438C,PCI\VEN_1002&DEV_4376"   
ms_1_isBusExtender=true

Folder \D\M\AM1\
It is included and should detect and support that controller / HDD

also

[AM2]
ms_count=1
ms_1_deviceName="AMD AHCI Compatible RAID 7xx"
ms_1_tag="ahci7xx"
ms_1_sysFile="ahci7xx.sys"
ms_1_hwids="{snip} PCI\VEN_1002&DEV_4393&SUBSYS_43931002 {snip}"
ms_1_isBusExtender=false

Folder \D\M\AM2\
It is included and should detect and support that RAID controller / HDD

Post your DPs_BASE.log please.
Your HDDs should be detected and installed... something is not right... your log will likely tell me what is wrong.

PS the output of the HWID's Tool was not posted in it's entirety...
Since you have a RAID controller i need the rest of the output... (IE it would also list the compatable HWIDs for that raid controller...)

What happens when you add DriverPack MassStorage textmode with DriverPacks BASE? (the supported way to add them)
mass storage textmode drivers are only about 6 meg... just add them with DriverPacks BASE...
easy...

What are the HWIDs?

Which OS (Service Pack Level and type [IE home, Pro, Retail, OEM, Corp])

Please see 'Read BEFORE you post' and supply some missing details

If you are dead set on adding them manually then MSFN.ORG is the place for answers...
(since x64 is not supported you have little choice for that)
http://unattended.msfn.org/unattended.x … bd84224c2/

Welcome aboard sir!

MSFN.ORG is where i would search

OffLine SysPrep does this now

if it was an official pack it would have been released

if a file version is over 4 numbers then it is a test pack (A Nightly)...

90503 is Five numbers and is therefore a test pack   (905 or 905x would be a final / official)

test packs are not intended for deployment... testing only!

about a gig of disc space more required for M1 however you can use devpath for KTD like features...

However since after the install the drivers are not needed and should be deleted it really doesn't matter where you put them since you will delete them... I would not put anything i was going to delete in system32... just in case

At what point are you calling the tool

GUIRunonce, RunOnceEX, Startup folder, Login script, autoexec.bat???

If you follow the thread i linked to above it is discussed in quite some detail...

post #14 is pretty clear... http://forum.driverpacks.net/viewtopic. … 857#p20857

read that and the FAQ for SAD...