Search options (Page 9 of 159)

Merry Christmas to you too.

Yes.  We typically recommend users only integrate dpms into boot.wim but in reality you can integrate whatever you want (Chipset, LAN, etc.).  But keep in mind that the more drivers you integrate into the boot.wim, the LONGER the boot process will take as ALL those drivers are loaded into RAM.  In the past, some users went through the ridiculous process of loading ALL the DriverPacks into the boot.wim.  While that would work, it would be very stupid.

No.  Drivers added to boot.wim only allow the installation utility to "see" the installation target (hard drive) or sources (DVD, USB, network share, etc.).  If a driver is needed by the system to "see" a drive controller, and the driver is only loaded into the boot.wim, then the installation (file copy stage) will go OK, but you'll likely get a BSOD during the later stages when no driver is found and the installer can't find the drive anymore.

Link is dead.  "It's dead Jim!"
*Edit
Link is here: http://www.ti.com/lit/sw/sllc423e/sllc423e.zip

I'm working on these NT6 dpms packs now.
I'll see what I can do.

You'll notice that Sony themselves don't support XP with that model.
If the manufacturer doesn't have a XP driver, finding a workable driver elsewhere will be like finding a needle in a haystack.

Upgrade to Win7 and call it a day.  You'll be much happier.

I haven't been looking at the test packs that you guys have been posting lately, but the last pack I built was 1210r1 and it does NOT have that generic HWID in the .ini.  That partial HWID (with either &CC*** or &SUBSYS***) is listed in these sections: [L](sub-section-8) and [I4](sub-section-1).  There's no overlap.

...moved from "Software" to "Universal Imaging"...

Have you changed the HAL?  I'm not sure DriverPacks is breaking your install. 
Hopefully one of our users more versed in WDS will chime in here.

Your first "for" loop is missing the end-quotes.  Change to read as below:

SET TAGFILE=\OEM
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) DO IF EXIST "%%i:\CD\WXPS\OEM" SET "CDDRIVE=%%i:\CD\WXPS" & GOTO DPsFound
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) DO DIR %%i: && IF EXIST "%%i:%TAGFILE%" SET "CDDRIVE=%%i:" & GOTO DPsFound
IF EXIST "\$win_nt$.~ls" SET CDDRIVE=\$win_nt$.~ls
:DPsFound

Here's a more refined expression of your mods:

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) DO (
 IF Exist "%%i:\OEM\bin\un7zip.exe" SET "DPLoc=%%i:\OEM" & Set "M=2"
 IF Exist "%%i:\$OEM$\$1\D\" (SET "DPLoc=%%i:\$OEM$\$1" & Set "M=1" & %%i)
 IF Exist "%%i:\CD\WXPS\OEM\bin\un7zip.exe" (SET "DPLoc=%%i:\CD\WXPS\OEM" & Set "M=2")
 IF "!M!" GEQ "1" GoTo Found
)

Actually, dpinst.exe is one of the few M$ products that they actively encourage free distribution.  They wrote that into their EULA in the "driver distribution kit" (can't remember the name).

Wow, that's awesome.  This is a collaborative effort.  Of course I don't mind!
Please upload it to mediafire or other free hosting service and I'll verify it.

Yes.  I've seen that happen too.  I am working on a new revision and hopefully will have that sorted out.
In the meantime, the easiest method to avoid the problem is to hit the Windows key, type "cmd", then right click on cmd.exe and "run as administrator", then execute DP_Install_Tool.cmd /S

The instructions are in the first post of the SAD2 thread and in the "readme.txt" included in the download.
The hotfix is KB888111 but there's no reason not to use SP3.