• cHarOn
  • DriverPacks newbie
  • Offline
  • Registered: 2006-05-28
  • Posts: 13

Topic: [NEEDS REPLY] [sysprep] Can't find DPSfinisher.exe

I have an little Problem not that hard but it would be interresting for me!!

When i make an Windows Preinstallation everything works like an charm ;-)
but when i seal then windows with the sysprep tool and the reopen windows i get an error c:\DPsFnshr.exe cant found!!
It is only cosmetic but where is the entrie in which file were it creates it that it schould start the prog?!
Can i remove the entrie when i finished the first login??

greatz cHarOn

  • Jaak
  • Old Timer Rookie
  • Offline
  • From: Eeklo, in the East Flanders
  • Registered: 2006-07-23
  • Posts: 3,594

Re: [NEEDS REPLY] [sysprep] Can't find DPSfinisher.exe

hi

DpsBase adds these lines to Winnt.sif

[Data]
MsDosInitiated=No


[GUIRunOnce]
command9="%SystemDrive%\DPsFnshr.exe"

The answer was 42?
Kind regards, Jaak.
  • From: Hasselt, Belgium
  • Registered: 2006-05-26
  • Posts: 2,609

Re: [NEEDS REPLY] [sysprep] Can't find DPSfinisher.exe

You say that you are using Sysprep. Then have you applied the appropriate changes? Did you for example extract DPsFnshr.7z to %systemdrive% and copy DPsFnshr.ini there too?

Founder of DriverPacks.net — wimleers.com

Wim Leers's Website

  • cHarOn
  • DriverPacks newbie
  • Offline
  • Registered: 2006-05-28
  • Posts: 13

Re: [NEEDS REPLY] [sysprep] Can't find DPSfinisher.exe

You say that you are using Sysprep. Then have you applied the appropriate changes? Did you for example extract DPsFnshr.7z to %systemdrive% and copy DPsFnshr.ini there too?

no i didnt extract them can you tell me for what i need to do that? Bashrat this is the way i install.
1.) Windows CD modified with all updates and driverpacks included special for the Masstorage thing Dpsfinisher works without an error
2.) Install all Software I need
3.) Then seal with sysprep.exe
4.) Reopen Windows and then the error comes up

it is for me normal because dpsfinisher deletes the files after first login but then there would be nice when the dpsfinisher deletes the files that it also deletes the entries which starts the dpsfinisher. And where gets the finisher started.

@jtdoom: Thanks for that info but the winnt.sif is not avaible under windows only on the windows cd?!?!

Thx for your tips and tricks hehe

cHarOn

Last edited by cHarOn (2006-10-14 18:56:22)

  • cHarOn
  • DriverPacks newbie
  • Offline
  • Registered: 2006-05-28
  • Posts: 13

Re: [NEEDS REPLY] [sysprep] Can't find DPSfinisher.exe

no Idea anymore?!?!?!

  • From: Seattle
  • Registered: 2006-10-27
  • Posts: 24

Re: [NEEDS REPLY] [sysprep] Can't find DPSfinisher.exe

I would LOVE to find the official updated instructions for using Sysprep with the C++ version of BASE.  Are these posted anywhere?

skinlayers

  • From: Hasselt, Belgium
  • Registered: 2006-05-26
  • Posts: 2,609

Re: [NEEDS REPLY] [sysprep] Can't find DPSfinisher.exe

skinlayers wrote:

I would LOVE to find the official updated instructions for using Sysprep with the C++ version of BASE.  Are these posted anywhere?

skinlayers

From an e-mail to some one else:

myself wrote:

So this is what you need to do:
1) Prepare everything for sysprep (create the C:\Sysprep directory and copy all files there).

2) Extract all DriverPacks you'd like to use to C:\, you'll end up with a directory C:\D and many subfolders below that.

3) Get DevPath.exe and execute this command:
    DevPath.exe C:\D

4) Copy DevPath.exe and DPsFnshr.ini to C:\, extract DPsFnshr.7z to C:\. (Do not forget this step!)

5) Add to the GUIRunOnce section of sysprep.inf these two commands:
    C:\DPsFnshr.exe
    C:\DevPath.exe

6) Run Sysprep.

7) Deploy!

That's all wink

Last edited by Bâshrat the Sneaky (2006-10-27 19:45:51)

Founder of DriverPacks.net — wimleers.com

Wim Leers's Website

  • From: Seattle
  • Registered: 2006-10-27
  • Posts: 24

Re: [NEEDS REPLY] [sysprep] Can't find DPSfinisher.exe

Bâshrat the Sneaky wrote:

4) Copy/extract all attached files to C:\. (Do not forget this step!)

This is the only part I'm confused on.  I figured out that you get devpath.exe out of \bin\wnt5_x86-32\M2.7z, and DPsFnshr.exe out of \bin\DPsFnshr.7z from BASE.  Is there anything else you need to place in C:\ other than the contents of M2.7z and DPsFnsh.7z?  Does all of \bin and \bin\wnt5_x86-32 need to be copied and/or extracted to C:\?

Thanks again!

  • From: Hasselt, Belgium
  • Registered: 2006-05-26
  • Posts: 2,609

Re: [NEEDS REPLY] [sysprep] Can't find DPSfinisher.exe

skinlayers wrote:
Bâshrat the Sneaky wrote:

4) Copy/extract all attached files to C:\. (Do not forget this step!)

This is the only part I'm confused on.  I figured out that you get devpath.exe out of \bin\wnt5_x86-32\M2.7z, and DPsFnshr.exe out of \bin\DPsFnshr.7z from BASE.  Is there anything else you need to place in C:\ other than the contents of M2.7z and DPsFnsh.7z?  Does all of \bin and \bin\wnt5_x86-32 need to be copied and/or extracted to C:\?

Thanks again!

My bad!

I've updated that one entry in my previous post:

corrected myself wrote:

4) Copy DevPath.exe and DPsFnshr.ini to C:\, extract DPsFnshr.7z to C:\. (Do not forget this step!)

Founder of DriverPacks.net — wimleers.com

Wim Leers's Website

  • From: Seattle
  • Registered: 2006-10-27
  • Posts: 24

Re: [NEEDS REPLY] [sysprep] Can't find DPSfinisher.exe

Thanks, Bâshrat!

Unfortunately, now I have a different problem.  After running SysPrep and rebooting, DPsFnshr.exe runs and gives the error:

"The DriverPacks root directory in the settings file doesn't contain a valid DriverPacks directory structure!"

From what I understand, I don't need to run DPs_BASe.exe at any point.  Do I need to edit the DPsFnshr.ini manually and point it to C:\D (or %SystemDrive%\D)? 

Here is my DPsFnshr.ini

[Settings]
; DO NOT SET THIS MANUALLY, LET THE DriverPacks BASE DO IT FOR YOU! (may NOT contain any spaced, if it does, all exceptions must be adapted to be compatible!)
DPsRoot	= "%SystemDrive%"
; DO NOT SET THIS MANUALLY, LET THE DriverPacks BASE DO IT FOR YOU!
KTD	= ""
; system variables supported: %SystemDrive%, %SystemRoot% and %WinDir%, one
; location cannot be used as KTDlocation: the root directory specified in
; [Settings]\DPsRoot
KTDlocation	= "%SystemRoot%\DriverPacks"


; =============================================================================
;
; REMARKS
;
; =============================================================================
; -----------------------------------------------------------------------------
; About adding your own exceptions
; -----------------------------------------------------------------------------
;
; - The following system variables are supported:
;  * %SystemDrive%
;  * %SystemRoot%
;  * %WinDir%
;  * %ProgramFiles%
;  * %DPSROOT% (equals the value of [Settings]\DPsRoot)
;  * %DPSTMP% (when you must extract files for example)
;
; - Available executables:
;  * addUsepmtimer.exe
;  * devcon.exe
;
; - The unique ID in the sectionnames (i.e.: [<OS platform>__<unique ID>__
;   <driver dir, including the master 'D' dir>]) must NOT be sequential, it
;   must just be unique. Only numbers (0-9) can be used. The reason for the
;   existence of this string is that sometimes there are multiple exceptions
;   for the same driver, which would result in identical section names, which
;   is not allowed.
;
; - A requirement of the type 'tagFiles' is considered forfilled if ALL of the
;   listed conditions are met.
;
; - A requirement of the types '+hwids', '-hwids', '+infFiles' and '-infFiles'
;   is considered forfilled if ANY of the listed conditions is met.
;
; - The commands will ONLY be executed if ALL the active requirements are
;
; - The commands will be executed in the order they are entered.
;
;
; -----------------------------------------------------------------------------
; About the implementation of KTD
; -----------------------------------------------------------------------------
;
; - To optimize the DevicePath entry in the registry (to allow more drivers to
;   be added), a new system variable will be created, which will accessible
;   through the variable %KTD%. The result is that each path that is added
;   (that refers to a driver), will be much shorter - and therefore this allows
;   more drivers to be added.
;
; =============================================================================

[wnt5_x86-32__0000__D]
tagFiles	= 0
+hwids		= 1
+hwid1		= "ACPI\MGMT180"
-hwids		= 0
+infFiles	= 0
-infFiles	= 0
commands	= 1
command1	= "%SystemDrive%\devcon.exe remove ACPI\MGMT180"


[wnt5_x86-32__0001__D-CP]
tagFiles	= 0
+hwids		= 1
+hwid1		= "ACPI\AUTHENTICAMD_-_X86_FAMILY_15_MODEL_35"
-hwids		= 0
+infFiles	= 0
-infFiles	= 0
commands	= 1
command1	= "%SystemDrive%\pmtimer.exe"


[wnt5_x86-32__0002__D-G-A-1]
tagFiles	= 2
tagFile1	= "%SystemDrive%\ATICCC.ins"
tagFile2	= "%DPSROOT%\D\G\A\1\ATICCC.exe"
+hwids		= 0
-hwids		= 0
+infFiles	= 1
+infFile1	= "%DPSROOT%\D\G\A\1\*.inf"
-infFiles	= 0
commands	= 6
command1	= "%DPSROOT%\D\G\A\1\ATICCC.exe -y -o%DPSTMP%"
command2	= "msiexec /i %DPSTMP%\ISScript9.Msi /qn /norestart"
command3	= "?processWaitClose:ISScript9.Msi"
command4	= "msiexec /i %DPSTMP%\ATICCC.msi /qn /norestart"
command5	= "?processWaitClose:ATICCC.msi"
command6	= "rd /s /q %DPSTMP%"


[wnt5_x86-32__0003__D-G-A-1]
tagFiles	= 2
tagFile1	= "%SystemDrive%\ATICCP.ins"
tagFile2	= "%DPSROOT%\D\G\A\1\ATICCP.exe"
+hwids		= 0
-hwids		= 0
+infFiles	= 1
+infFile1	= "%DPSROOT%\D\G\A\1\*.inf"
-infFiles	= 0
commands	= 3
command1	= "%DPSROOT%\D\G\A\1\ATICCP.exe -y -o%DPSTMP%"
command2	= "start /wait %DPSTMP%\Setup.exe /K"
command3	= "rd /s /q %DPSTMP%"


[wnt5_x86-32__0004__D-G-A-2]
tagFiles	= 1
tagFile1	= "%DPSROOT%\D\G\A\2\CPanel.exe"
+hwids		= 0
-hwids		= 0
+infFiles	= 1
+infFile1	= "%DPSROOT%\D\G\A\2\*.inf"
-infFiles	= 0
commands	= 3
command1	= "%DPSROOT%\D\G\A\2\CPanel.exe -y -o%DPSTMP%"
command2	= "start /wait %DPSTMP%\setup.exe /K"
command3	= "rd /s /q %DPSTMP%"


[wnt5_x86-32__0005__D-G-A-5]
tagFiles	= 2
tagFile1	= "%SystemDrive%\ATICCP.ins"
tagFile2	= "%DPSROOT%\D\G\A\1\ATICCP.exe"
+hwids		= 0
-hwids		= 0
+infFiles	= 1
+infFile1	= "%DPSROOT%\D\G\A\5\*.inf"
-infFiles	= 0
commands	= 3
command1	= "%DPSROOT%\D\G\A\1\ATICCP.exe -y -o%DPSTMP%"
command2	= "start /wait %DPSTMP%\Setup.exe /K"
command3	= "rd /s /q %DPSTMP%"


[wnt5_x86-32__0006__D-G-A-5]
tagFiles	= 2
tagFile1	= "%SystemDrive%\ATICCC.ins"
tagFile2	= "%DPSROOT%\D\G\A\1\ATICCC.exe"
+hwids		= 0
-hwids		= 0
+infFiles	= 1
+infFile1	= "%DPSROOT%\D\G\A\5\*.inf"
-infFiles	= 0
commands	= 6
command1	= "%DPSROOT%\D\G\A\1\ATICCC.exe -y -o%DPSTMP%"
command2	= "msiexec /i %DPSTMP%\ISScript9.Msi /qn /norestart"
command3	= "?processWaitClose:ISScript9.Msi"
command4	= "msiexec /i %DPSTMP%\ATICCC.msi /qn /norestart"
command5	= "?processWaitClose:ATICCC.msi"
command6	= "rd /s /q %DPSTMP%"


[wnt5_x86-32__0007__D-G-3-1]
tagFiles	= 1
tagFile1	= "%SystemRoot%\system32\3dfxV2ps.dll"
+hwids		= 0
-hwids		= 0
+infFiles	= 1
+infFile1	= "%DPSROOT%\D\G\3\1\*.inf"
-infFiles	= 0
commands	= 1
command1	= "%DPSROOT%\D\G\3\1\V2_OC_control_panel.exe"


[wnt5_x86-32__0008__D-L-NV-123]
tagFiles	= 0
+hwids		= 1
+hwid1		= "PCI\VEN_10DE&DEV_00DF&SUBSYS_E0001458&REV_A2"
+hwid2		= "PCI\VEN_10DE&DEV_00DF&SUBSYS_02501462&REV_A2"
+hwid3		= "PCI\VEN_10DE&DEV_00DF&SUBSYS_A5511297&REV_A2"
-hwids		= 0
+infFiles	= 0
-infFiles	= 0
commands	= 2
command1	= "%SystemDrive%\devcon.exe update %DPSROOT%\D\L\NV\123\nvnetbus.inf "PCI\VEN_10DE&DEV_00DF&SUBSYS_*""
command2 	= "%SystemDrive%\devcon.exe update %DPSROOT%\D\L\NV\123\nvnetfd.inf "{1a3e09be-1e45-494b-9174-d7385b45bbf5}\NVNET_DEV00DF""



[wnt5_x86-32__0009__D-S-CR-1]
tagFiles	= 2
tagFile1	= "%SystemRoot%\system32\drivers\ha20x2k.sys"
tagFile2	= "%DPSROOT%\D\S\CR\1\Ctzapxx.ini"
+hwids		= 0
-hwids		= 0
+infFiles	= 1
+infFile1	= "%DPSROOT%\D\S\CR\1\*.inf"
-infFiles	= 0
commands	= 19
command1	= "expand -r %DPSROOT%\D\S\CR\1\*.* %DPSROOT%\CR\1"
command2	= "expand -r %DPSROOT%\D\S\CR\1\common\*.* %DPSROOT%\D\S\CR\1\common"
command3	= "expand -r %DPSROOT%\D\S\CR\1\common\i386\*.* %DPSROOT%\D\S\CR\1\common\i386"
command4	= "expand -r %DPSROOT%\D\S\CR\1\lang\*.* %DPSROOT%\D\S\CR\1\lang"
command5	= "expand -r %DPSROOT%\D\S\CR\1\lang\i386\*.* %DPSROOT%\D\S\CR\1\lang\i386"
command6	= "expand -r %DPSROOT%\D\S\CR\1\win2k_xp\*.* %DPSROOT%\D\S\CR\1\win2k_xp"
command7	= "expand -r %DPSROOT%\D\S\CR\1\win2k_xp\data\*.* %DPSROOT%\D\S\CR\1\win2k_xp\data"
command8	= "expand -r %DPSROOT%\D\S\CR\1\win2k_xp\i386\*.* %DPSROOT%\D\S\CR\1\win2k_xp\i386"
command9	= "del /q %DPSROOT%\D\S\CR\1\*.??_"
command10	= "del /q %DPSROOT%\D\S\CR\1\common\*.??_"s
command11	= "del /q %DPSROOT%\D\S\CR\1\common\i386\*.??_"
command12	= "del /q %DPSROOT%\D\S\CR\1\lang\*.??_"
command13	= "del /q %DPSROOT%\D\S\CR\1\lang\i386\*.??_"
command14	= "del /q %DPSROOT%\D\S\CR\1\win2k_xp\*.??_"
command15	= "del /q %DPSROOT%\D\S\CR\1\win2k_xp\data\*.??_"
command16	= "del /q %DPSROOT%\D\S\CR\1\win2k_xp\i386\*.??_"
command17	= "copy /y %DPSROOT%\D\S\CR\1\common\i386\CtCtlPan.cpl %SystemRoot%\system32\"
command18	= "copy /y %DPSROOT%\D\S\CR\1\common\i386\CtPanel.exe %SystemRoot%\system32\"
command19	= "start /wait %DPSROOT%\D\S\CR\1\CTZAPXX.exe /S"


[wnt5_x86-32__0010__D-S-CR-2]
tagFiles	= 3
tagFile1	= "%SystemRoot%\system32\drivers\ha10kx2k.sys"
tagFile2	= "%SystemRoot%\system32\drivers\ha20x2k.sys"
tagFile3	= "%DPSROOT%\D\S\CR\2\Ctzapxx.ini"
+hwids		= 0
-hwids		= 0
+infFiles	= 1
+infFile1	= "%DPSROOT%\D\S\CR\2\*.inf"
-infFiles	= 0
commands	= 19
command1	= "expand -r %DPSROOT%\D\S\CR\2\*.* %DPSROOT%\CR\2"
command2	= "expand -r %DPSROOT%\D\S\CR\2\common\*.* %DPSROOT%\D\S\CR\2\common"
command3	= "expand -r %DPSROOT%\D\S\CR\2\common\i386\*.* %DPSROOT%\D\S\CR\2\common\i386"
command4	= "expand -r %DPSROOT%\D\S\CR\2\lang\*.* %DPSROOT%\D\S\CR\2\lang"
command5	= "expand -r %DPSROOT%\D\S\CR\2\lang\i386\*.* %DPSROOT%\D\S\CR\2\lang\i386"
command6	= "expand -r %DPSROOT%\D\S\CR\2\win2k_xp\*.* %DPSROOT%\D\S\CR\2\win2k_xp"
command7	= "expand -r %DPSROOT%\D\S\CR\2\win2k_xp\data\*.* %DPSROOT%\D\S\CR\2\win2k_xp\data"
command8	= "expand -r %DPSROOT%\D\S\CR\2\win2k_xp\i386\*.* %DPSROOT%\D\S\CR\2\win2k_xp\i386"
command9	= "del /q %DPSROOT%\D\S\CR\2\*.??_"
command10	= "del /q %DPSROOT%\D\S\CR\2\common\*.??_"
command11	= "del /q %DPSROOT%\D\S\CR\2\common\i386\*.??_"
command12	= "del /q %DPSROOT%\D\S\CR\2\lang\*.??_"
command13	= "del /q %DPSROOT%\D\S\CR\2\lang\i386\*.??_"
command14	= "del /q %DPSROOT%\D\S\CR\2\win2k_xp\*.??_"
command15	= "del /q %DPSROOT%\D\S\CR\2\win2k_xp\data\*.??_"
command16	= "del /q %DPSROOT%\D\S\CR\2\win2k_xp\i386\*.??_"
command17	= "copy /y %DPSROOT%\D\S\CR\2\common\i386\CtCtlPan.cpl %SystemRoot%\system32\"
command18	= "copy /y %DPSROOT%\D\S\CR\2\common\i386\CtPanel.exe %SystemRoot%\system32\"
command19	= "start /wait %DPSROOT%\D\S\CR\2\CTZAPXX.exe /S"


[wnt5_x86-32__0011__D-S-CR-3]
tagFiles	= 2
tagFile1	= "%SystemRoot%\system32\drivers\P17.sys"
tagFile2	= "%DPSROOT%\D\S\CR\3\Ctzapxx.ini"
+hwids		= 0
-hwids		= 0
+infFiles	= 1
+infFile1	= "%DPSROOT%\D\S\CR\3\*.inf"
-infFiles	= 0
commands	= 14
command1	= "expand -r %DPSROOT%\D\S\CR\3\*.* %DPSROOT%\CR\3"
command2	= "expand -r %DPSROOT%\D\S\CR\3\AddOn\*.* %DPSROOT%\D\S\CR\3\AddOn"
command3	= "expand -r %DPSROOT%\D\S\CR\3\common\*.* %DPSROOT%\D\S\CR\3\common"
command4	= "expand -r %DPSROOT%\D\S\CR\3\Lang\i386\*.* %DPSROOT%\D\S\CR\3\Lang\i386"
command6	= "expand -r %DPSROOT%\D\S\CR\3\Win2K_XP\*.* %DPSROOT%\D\S\CR\3\Win2K_XP"
command7	= "expand -r %DPSROOT%\D\S\CR\3\Win2K_XP\i386\*.* %DPSROOT%\D\S\CR\3\Win2K_XP\i386"
command8	= "del /q %DPSROOT%\D\S\CR\3\*.??_"
command9	= "del /q %DPSROOT%\D\S\CR\3\Addon\*.??_"
command10	= "del /q %DPSROOT%\D\S\CR\3\common\*.??_"
command11	= "del /q %DPSROOT%\D\S\CR\3\Lang\i386\*.??_"
command12	= "del /q %DPSROOT%\D\S\CR\3\Win2K_XP\*.??_"
command13	= "del /q %DPSROOT%\D\S\CR\3\Win2k_XP\i386\*.??_"
command14	= "start /wait %DPSROOT%\D\S\CR\3\CTZapxx.Exe /S"


[wnt5_x86-32__0012__D-S-H-2]
tagFiles	= 0
+hwids		= 0
-hwids		= 0
+infFiles	= 1
+infFile1	= "%DPSROOT%\D\S\H\2.inf"
-infFiles	= 0
commands	= 4
command1	= "%SystemDrive%\devcon.exe disable =net"
command2	= "%SystemDrive%\devcon.exe updateni %DPSROOT%\D\S\H\2\wdmaherc.inf "PCI\VEN_1013&DEV_6003&SUBSYS_*""
command3	= "%SystemDrive%\devcon.exe updateni %DPSROOT%\D\S\H\2\wdmaherc.inf "HERCULES\*""
command4	= "%SystemDrive%\devcon.exe enable =net"


[wnt5_x86-32__0013__D-S-N]
tagFiles	= 1
tagFile1	= "%SystemRoot%\system32\drivers\nvapu.sys"
+hwids		= 0
-hwids		= 0
+infFiles	= 1
+infFile1	= "%DPSROOT%\D\S\N\*.inf"
-infFiles	= 0
commands	= 3
command1	= "start /wait %DPSROOT%\D\S\N\AudioUtl.exe -y -o%DPSTMP%"
command2	= "start /wait %DPSTMP%\Setup.exe -s -f1"
command3	= "rd /s /q %DPSTMP%"


[wnt5_x86-32__0014__D-S-S-U]
tagFiles	= 1
tagFile1	= "%SystemRoot%\system32\drivers\sthda.sys"
+hwids		= 0
-hwids		= 0
+infFiles	= 1
+infFile1	= "%DPSROOT%\D\S\S\U\3\*.inf"
-infFiles	= 0
commands	= 6
command1	= "copy /y %DPSROOT%\D\S\S\U\stlang.dll %SystemRoot%\system32"
command2	= "copy /y %DPSROOT%\D\S\S\U\stacgui.dll %SystemRoot%\system32"
command3	= "copy /y %DPSROOT%\D\S\S\U\stacgui.cpl %SystemRoot%\system32"
command4	= "md "%ProgramFiles%\Sigmatel\C-Major Audio\STACGUI""
command5	= "copy /y %DPSROOT%\D\S\S\U\sttray.exe "%ProgramFiles%\Sigmatel\C-Major Audio\STACGUI""
command6	= "copy /y %DPSROOT%\D\S\S\U\stlang.dll "%ProgramFiles%\Sigmatel\C-Major Audio\WDM""


[wnt5_x86-32__0015__D-S-SI-1]
tagFiles	= 1
tagFile1	= "%SystemRoot%\system32\drivers\sis7012.sys"
+hwids		= 0
-hwids		= 0
+infFiles	= 1
+infFile1	= "%DPSROOT%\D\S\SI\1\*.inf"
-infFiles	= 0
commands	= 1
command1	= "start /wait %DPSROOT%\D\S\SI\1\SI_7012.exe x -y o%SystemRoot%\"


[wnt5_x86-32__0016__D-S-SI-2]
tagFiles	= 1
tagFile1	= "%SystemRoot%\system32\drivers\sis7018.sys"
+hwids		= 0
-hwids		= 0
+infFiles	= 1
+infFile1	= "%DPSROOT%\D\S\SI\2\*.inf"
-infFiles	= 0
commands	= 1
command1	= "start /wait %DPSROOT%\D\S\SI\2\SI_7018.exe x -y o%SystemRoot%\"


[wnt5_x86-32__0017__D-S-T-2]
tagFiles	= 1
tagFile1	= "%SystemRoot%\system32\drivers\FM801.sys"
tagFile1	= "%DPSROOT%\D\S\T\2\Setup.ex_"
+hwids		= 0
-hwids		= 0
+infFiles	= 1
+infFile1	= "%DPSROOT%\D\S\T\2\*.inf"
-infFiles	= 0
commands	= 3
command1	= "expand -r %DPSROOT%\D\S\T\2\*.* %DPSROOT%\D\S\T\2"
command2	= "del /q %DPSROOT%\D\S\T\2\*.??_"
command3	= "start /wait %DPSROOT%\D\S\T\2\Setup.exe /S"


[wnt5_x86-32__0018__D-S-T-3]
tagFiles	= 1
tagFile1	= "%SystemRoot%\system32\drivers\cmaudio.sys"
+hwids		= 0
-hwids		= 0
+infFiles	= 1
+infFile1	= "%DPSROOT%\D\S\T\3\*.inf"
-infFiles	= 0
commands	= 1
command1	= "start /wait %DPSROOT%\D\S\T\3\T_3.exe"

[wnt5_x86-32__0019__D-S-T-4]
tagFiles	= 1
tagFile1	= "%SystemRoot%\system32\drivers\TT1724ht.sys"
+hwids		= 0
-hwids		= 0
+infFiles	= 1
+infFile1	= "%DPSROOT%\D\S\T\4\*.inf"
-infFiles	= 0
commands	= 1
command1	= "start /wait %DPSROOT%\D\S\T\4\T_SSU.exe"


[wnt5_x86-32__0020__D-S-T-5]
tagFiles	= 1
tagFile1	= "%SystemRoot%\system32\drivers\dmxsens.sys"
+hwids		= 0
-hwids		= 0
+infFiles	= 1
+infFile1	= "%DPSROOT%\D\S\T\5\*.inf"
-infFiles	= 0
commands	= 1
command1	= "start /wait %DPSROOT%\D\S\T\5\T_DMX.exe"


[wnt5_x86-32__0021__D-S-V-1]
tagFiles	= 1
tagFile1	= "%SystemRoot%\system32\drivers\envysens.sys"
tagFile1	= "%DPSROOT%\D\S\V\1\V_ENVY.exe"
+hwids		= 0
-hwids		= 0
+infFiles	= 1
+infFile1	= "%DPSROOT%\D\S\V\1\*.inf"
-infFiles	= 0
commands	= 1
command1	= "start /wait %DPSROOT%\D\S\V\1\V_ENVY.exe -y -o%SystemRoot%\"


[wnt5_x86-32__0022__D-S-V-2]
tagFiles	= 2
tagFile1	= "%SystemRoot%\system32\drivers\vinyl97.sys"
tagFile2	= "%DPSROOT%\D\S\V\2\V_VINYL.exe"
+hwids		= 0
-hwids		= 0
+infFiles	= 1
+infFile1	= "%DPSROOT%\D\S\V\2\*.inf"
-infFiles	= 0
commands	= 1
command1	= "start /wait %DPSROOT%\D\S\V\2\V_VINYL.exe -y -o%SystemRoot%\"

And DPsFnshr.log

2006-10-31 09:31:08 : <INIT> DriverPacks Finisher 6.10 initialized.
2006-10-31 09:31:08 : <INIT> Splash screen initialized.
2006-10-31 09:31:08 : <INIT> Detected platform wnt5_x86-32.
2006-10-31 09:31:08 : <INIT> Start logging of the HWIDs for relevant devices present in this system.
2006-10-31 09:31:08 : <INIT> 1. ACPI devices

ACPI\FIXEDBUTTON\2&DABA3FF&0                                : ACPI Fixed Feature Button
ACPI\GENUINEINTEL_-_X86_FAMILY_15_MODEL_3\_0                : Intel(R) Pentium(R) 4 CPU 3.00GHz
ACPI\GENUINEINTEL_-_X86_FAMILY_15_MODEL_3\_1                : Intel(R) Pentium(R) 4 CPU 3.00GHz
ACPI\PNP0000\4&247BCBC6&0                                   : Programmable interrupt controller
ACPI\PNP0003\1                                              : Advanced programmable interrupt controller
ACPI\PNP0100\4&247BCBC6&0                                   : System timer
ACPI\PNP0200\4&247BCBC6&0                                   : Direct memory access controller
ACPI\PNP0303\4&247BCBC6&0                                   : Standard 101/102-Key or Microsoft Natural PS/2 Keyboard
ACPI\PNP0401\4&247BCBC6&0                                   : ECP Printer Port (LPT1)
ACPI\PNP0501\1                                              : Communications Port (COM1)
ACPI\PNP0700\4&247BCBC6&0                                   : Standard floppy disk controller
ACPI\PNP0800\4&247BCBC6&0                                   : System speaker
ACPI\PNP0A03\2&DABA3FF&0                                    : PCI bus
ACPI\PNP0B00\4&247BCBC6&0                                   : System CMOS/real time clock
ACPI\PNP0C01\2&DABA3FF&0                                    : System board
ACPI\PNP0C02\1                                              : Motherboard resources
ACPI\PNP0C02\2                                              : Motherboard resources
ACPI\PNP0C04\4&247BCBC6&0                                   : Numeric data processor
ACPI\PNP0C0C\2&DABA3FF&0                                    : ACPI Power Button
ACPI\PNP0F13\4&247BCBC6&0                                   : PS/2 Compatible Mouse
ACPI_HAL\PNP0C08\0                                          : Microsoft ACPI-Compliant System
ROOT\ACPI_HAL\0000                                          : Advanced Configuration and Power Interface (ACPI) PC
22 matching device(s) found.

2006-10-31 09:31:08 : <INIT> 2. PCI devices

PCI\VEN_14E4&DEV_1696&SUBSYS_12BC103C&REV_03\4&2C4CBB84&0&10F0: Broadcom NetXtreme Gigabit Ethernet for hp
PCI\VEN_8086&DEV_244E&SUBSYS_00000000&REV_C2\3&61AAA01&3&F0 : Intel(R) 82801DB PCI Bridge - 244E
PCI\VEN_8086&DEV_24D0&SUBSYS_00000000&REV_02\3&61AAA01&3&F8 : Intel(R) 82801EB LPC Interface Controller - 24D0
PCI\VEN_8086&DEV_24D1&SUBSYS_12BC103C&REV_02\3&61AAA01&3&FA : Intel(R) 82801EB Ultra ATA Storage Controllers - 24D1
PCI\VEN_8086&DEV_24D2&SUBSYS_12BC103C&REV_02\3&61AAA01&3&E8 : Intel(R) 82801EB USB Universal Host Controller - 24D2
PCI\VEN_8086&DEV_24D4&SUBSYS_12BC103C&REV_02\3&61AAA01&3&E9 : Intel(R) 82801EB USB Universal Host Controller - 24D4
PCI\VEN_8086&DEV_24D5&SUBSYS_12BC103C&REV_02\3&61AAA01&3&FD : SoundMAX Integrated Digital Audio
PCI\VEN_8086&DEV_24D7&SUBSYS_12BC103C&REV_02\3&61AAA01&3&EA : Intel(R) 82801EB USB Universal Host Controller - 24D7
PCI\VEN_8086&DEV_24DB&SUBSYS_12BC103C&REV_02\3&61AAA01&3&F9 : Intel(R) 82801EB Ultra ATA Storage Controllers - 24DB
PCI\VEN_8086&DEV_24DD&SUBSYS_12BC103C&REV_02\3&61AAA01&3&EF : Intel(R) 82801EB USB2 Enhanced Host Controller - 24DD
PCI\VEN_8086&DEV_2570&SUBSYS_00000000&REV_02\3&61AAA01&3&00 : Intel(R) 82865G/PE/P/GV/82848P Processor to I/O Controller - 2570
PCI\VEN_8086&DEV_2572&SUBSYS_12BC103C&REV_02\3&61AAA01&3&10 : Intel(R) 82865G Graphics Controller
12 matching device(s) found.

2006-10-31 09:31:08 : <INIT> 3. HDAUDIO devices

No matching devices found.

2006-10-31 09:31:08 : <INIT> 4. USB devices

USB\ROOT_HUB\4&29FDE0AD&0                                   : USB Root Hub
USB\ROOT_HUB\4&316A71EE&0                                   : USB Root Hub
USB\ROOT_HUB\4&73B8598&0                                    : USB Root Hub
USB\ROOT_HUB20\4&F2E88BD&0                                  : USB Root Hub
4 matching device(s) found.

2006-10-31 09:31:08 : <INIT> Logging of HWIDs complete.
[b]2006-10-31 09:31:08 : <CRIT> The DriverPacks root directory in the settings file doesn't contain a valid DriverPacks directory structure![/b]
2006-10-31 09:31:13 : <CLNP> Deleted "C:\DPsFnshr.ini"!
2006-10-31 09:31:13 : <CLNP> Deleted "C:\devcon.exe"!
2006-10-31 09:31:13 : <CLNP> Deleted "C:\makePNF.exe"!
2006-10-31 09:31:13 : <CLNP> Deleted "C:\pmtimer.exe"!
2006-10-31 09:31:13 : <CLNP> Deleted "C:\DSPdsblr.exe"!
2006-10-31 09:31:13 : <CLNP> Added new value to the RunOnce key in the registry: the DriverPacks Finisher itself will get deleted after the next reboot.
2006-10-31 09:31:13 : Program terminated.

Also, I assume if I want to save some space, I could place the extracted drivers folder "D" inside of C:\sysprep, except for GuiRunOnce runs after the SysPrep folder deletes itself (I'm assuming) which I think would cause problems for DPsFnshr.exe. 

Thanks again for all your help!

  • Fordy
  • DriverPacks newbie
  • Offline
  • Registered: 2006-07-17
  • Posts: 1

Re: [NEEDS REPLY] [sysprep] Can't find DPSfinisher.exe

I'm having the same problem:

"The DriverPacks root directory in the settings file doesn't contain a valid DriverPacks directory structure!"

Has anyone had success with SYSPREP and DriverPacks?

  • From: Seattle
  • Registered: 2006-10-27
  • Posts: 24

Re: [NEEDS REPLY] [sysprep] Can't find DPSfinisher.exe

Updated instructions for using DriverPacks with Sysprep broken off into its own thread here.

skinlayers

Last edited by skinlayers (2007-06-20 11:29:00)

  • OverFlow
  • DriverPacks Administrator & BASE Developer
  • Offline
  • From: Cincinnati
  • Registered: 2006-12-02
  • Posts: 6,730

Re: [NEEDS REPLY] [sysprep] Can't find DPSfinisher.exe

my guess is it is in the inf for the Hdaudbus.sys driver

a case sensitive search may yeild results since normaly it is i386 not I386 with the capital I
so you may get lucky

DP BartPE Tutorial   DP_BASE Tutorial   HWID's Tool     Read BEFORE you post    UserBars!
http://driverpacks.net/userbar/admin-1.png
The DriverPacks, the DP_Base program, and Support Forum are FREE!.

OverFlow's Website

  • Registered: 2007-03-30
  • Posts: 10

Re: [NEEDS REPLY] [sysprep] Can't find DPSfinisher.exe

Hey all, I found this site awhile ago and have played with the Driver Packs a bit, but until recently I haven't had the time to attempt what I ultimately wanted to do. I want to make a truly universal XP image that can be put on virtually any pc. Now from my understanding of how the Driver Packs work, I could make a Windows install CD w/ the DP integrated and the KTD option, install this on a base peice of hardware (well actually I'm using Virtual PC right now), sysprep it, then be able to deploy that image to various machines. This seems like a simpler process than what was being discussed a bit earlier in this thread, but since Bashrat is saying to do it that way, I'm curious if the way I want to do it will work fine. Any comments or suggestions would be appreciated guys, thanks a lot.

  • Registered: 2006-12-19
  • Posts: 54

Re: [NEEDS REPLY] [sysprep] Can't find DPSfinisher.exe

I have created images using this process on a Dell Optiplex GX745, and a GX620.   These images load and go through the initial configuration (driver installation, computer name, domain join) but after reboot, they lockup booting on a Dell Latitude C610 and D600.

Has anyone gotten images created on new desktops to work on these laptops?

  • Registered: 2006-12-19
  • Posts: 54

Re: [NEEDS REPLY] [sysprep] Can't find DPSfinisher.exe

Maybe I'm doing something wrong... my Sysprep OEMPNPDRIVERS section looks like this:

OemPnpDriversPath="D\3\CBSH\01\01_D600;D\3\CBSH\01\01_D610;D\3\CBSH\01\01_D620;D\3\CBSH\01\01_GX150;D\3\CBSH\01\01_GX260

My DPsFnsher.ini looks like this:

[Settings]
; DO NOT SET THIS MANUALLY, LET THE DriverPacks BASE DO IT FOR YOU! (may NOT contain any spaced, if it does, all exceptions must be adapted to be compatible!)
DPsRoot	= "%SystemDrive%"
; DO NOT SET THIS MANUALLY, LET THE DriverPacks BASE DO IT FOR YOU!
KTD = "FALSE"
; system variables supported (see remarks for a list) one location cannot be used as
; KTDlocation: the root directory specified in[Settings]\DPsRoot
KTDlocation	= ""
; system variables supported (see remarks for a list)
logLocation = "%SystemRoot%"
; enables/disables debug mode (enabled by default)
debug = "true"

And I am running "DevPath.exe C:\D" then executing sysprep (with all the changes above)

Everything is working fine except when drivers are searched for by windows they come up as:

C:\d\D\CBSH\01\01_D600\ATIetc.sys

...with that extra "D"

Is this due to running "DevPath.exe C:\D"?  Should I just be executing ""DevPath.exe C:\" (without the D) to correct this (or removing the D's from my Sysprep.INF)?  Or am I looking in the wrong place for this problem.

  • OverFlow
  • DriverPacks Administrator & BASE Developer
  • Offline
  • From: Cincinnati
  • Registered: 2006-12-02
  • Posts: 6,730

Re: [NEEDS REPLY] [sysprep] Can't find DPSfinisher.exe

you answered your own question yes you did! DevPath.exe C:\

Last edited by OverFlow (2007-05-16 15:14:55)

DP BartPE Tutorial   DP_BASE Tutorial   HWID's Tool     Read BEFORE you post    UserBars!
http://driverpacks.net/userbar/admin-1.png
The DriverPacks, the DP_Base program, and Support Forum are FREE!.

OverFlow's Website

  • Registered: 2006-12-19
  • Posts: 54

Re: [NEEDS REPLY] [sysprep] Can't find DPSfinisher.exe

Thank you sir!

  • From: Seattle
  • Registered: 2006-10-27
  • Posts: 24

Re: [NEEDS REPLY] [sysprep] Can't find DPSfinisher.exe

EvilBetty wrote:

Maybe I'm doing something wrong... my Sysprep OEMPNPDRIVERS section looks like this:

OemPnpDriversPath="D\3\CBSH\01\01_D600;D\3\CBSH\01\01_D610;D\3\CBSH\01\01_D620;D\3\CBSH\01\01_GX150;D\3\CBSH\01\01_GX260

If you are running "DevPath C:\D" then you do not need the OemPnpDriversPath in sysprep.inf.  DevPath.exe writes to the same registry entry, but doesn't have the 4096 byte limit that OemPnpDriversPath does.

  • From: Seattle
  • Registered: 2006-10-27
  • Posts: 24

Re: [NEEDS REPLY] [sysprep] Can't find DPSfinisher.exe

OverFlow wrote:

my guess is it is in the inf for the Hdaudbus.sys driver

a case sensitive search may yeild results since normaly it is i386 not I386 with the capital I
so you may get lucky

I tracked the issue down to using RyanVM's update packs.  Slipstreaming JUST SP2 (with nlite) and nothing else has helped eliminate a LOT of my imaging issues.

skinlayers

  • Registered: 2007-07-03
  • Posts: 5

Re: [NEEDS REPLY] [sysprep] Can't find DPSfinisher.exe

Hello,

i'm using the driverpacks for a while now and have the same problem as stated on top of this post.
When a installation is resealt with sysprep there should be no need to start the finisher at next login because the whole installation is already done. I also know that this is only cosmetic and one only has to click the error away but it is very annoying. When the finisher is run during the installation it should remove itself entirely and that is what the program does not do. It's a pitty because it all works so beautifull.
- Creating a unattended dvd with the updatepacks from ryan vm
- adding the driverpacks
- create the image and write it on dvd

Then one can put that dvd into any pc or notebook and it installs everything perfectly. I tested it on many devices.
The only problem ( cosmetic ) is when i try to reseal with sysprep so the first time the pc or notebook is booted up the user only has to put in the username and a few setting with the windows serial, there comes the error that windows can not find the finisher program. ( Windows has no need to search for that program because it is not neccecary anymore.

Probably the finisher leaves something somewhere in the registry to make the program start the first time it's bootup with an new user and it's just that place in the registry that i would like to know so i can remove it before i do a sysprep.

Is there someone who knows where the entry is hidden in the registry?