Unzip the SAD3 folder inside the extracted Windows folder of ISO and add the lines below in your autounattend.xmL file:

<settings pass="oobeSystem">
    <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
        <FirstLogonCommands>
            <SynchronousCommand wcm:action="add">
                <Description>SAD3</Description>
                <Order>3</Order>
                <CommandLine>cmd /q /c for %i in (C D E F G H I J K L M N O P Q R S T U V W X Y Z) do if exist %i:\SAD3\DP_Install_Tool.cmd start /wait %i:\SAD3\DP_Install_Tool.cmd /S</CommandLine>
                <RequiresUserInput>false</RequiresUserInput>
            </SynchronousCommand>
        </FirstLogonCommands>
    </component>
    <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
        <FirstLogonCommands>
            <SynchronousCommand wcm:action="add">
                <Description>SAD3</Description>
                <Order>3</Order>
                <CommandLine>cmd /q /c for %i in (C D E F G H I J K L M N O P Q R S T U V W X Y Z) do if exist %i:\SAD3\DP_Install_Tool.cmd start /wait %i:\SAD3\DP_Install_Tool.cmd /S</CommandLine>
                <RequiresUserInput>false</RequiresUserInput>
            </SynchronousCommand>
        </FirstLogonCommands>
    </component>
</settings>

Then create the ISO again and you're done.

Thanks for the fast reply and congratulations for its excellent script!

Hi mr_smartepants

I am inexperienced and am trying to integrate drivers in my image of Windows 7.

My doubt: driverpacks Chipset must be integrated in Boot.wim or Install.wim?

Thanks

4

(8 replies, posted in Other)

OK. After the aid of the friends of this site, I started to make the integration of isolated form, that is, with the off AV and without having access the Internet until the conclusion of the process. Thus I am sufficient insurance and the process was much more fast. 

Debtor for the attention!

5

(8 replies, posted in Other)

Thanks a lot, BigBrit

I made a test now and occurred this exactly. Also use the ESET and in the test that I made now, with the activated antivirus, the process came back to be slow and delayed about 12 minutes concluding.

Solved!

6

(8 replies, posted in Other)

Thanks OverFlow, here my DPs_BASE.log:

Process in 1 minutes and 6 seconds:
http://www.4shared.com/file/ZeSP5ibj/DP … 10-33.html

Process in 11 minutes and 21 seconds:
http://www.4shared.com/file/znE8M1vu/DP … 12-56.html

7

(8 replies, posted in Other)

Debtor for its reply.  It is that of the previous times that I made the process, the part of masstorage was more delayed and now is very fast, therefore I was in the doubt if the integration occurred without problems.

8

(8 replies, posted in Other)

Before, the process to integrate driverpacks delayed about 15 minutes… 
Using the same archives, with new version 10.06, the process was concluded in less than 2 minutes… 

It will be that I am making something made a mistake or this is correct?