Closed...

every thing is done unattended & worked properly
DriverPacks decompressed at the early stage of GUI Mode
drivers installed well as normal at T35
what i did ?
i deactivate the finisher and used my above method to install any new added HW manually

what i did now is instead of 24 packs to be decompressed at the early stage of GUI Mode i use only the main 10 packs u provide to save time
the other packs i kept them for the manual method as discribed above

now...
i got small problem that is
my machine has two display adaptors one is integrated with
the MB the other is detached
although i disabled integrated one from the Bios
but is still is recognized by windows
& both are installed during unattended installation
the problem is my desktop icons disappeared
i restore them when i disabled integrated display adaptor from
Device Manager

will this problem get corrected in my next installation when i allow the
finisher runs as normal during Runonceex stage?

iam going to test this
****
no more KTD selection
********
Mr OverFlow
from the DP_Install_Tool.cmd file
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
****************************************
what is this command *******& %%i******** doing?

Also, do you use nLite, AutoImage, HFSlip or any other program to trim and automate your installs?

----

PS my frustration lies in him not finding out what the finisher does without me typing it out... again.
IT'S IN the FAQ forum for Pete's sake! how hard is that to find...
- the finisher is the core of DriverPacks
   Bâshrat the Sneaky wrote  (in that FAQ forum post you did not find) http://forum.driverpacks.net/viewtopic.php?id=364

DriverPacks Finisher: this program handles all exceptions (mainly control panels, but it also fixes some drivers that would always get installed incorrectly), KTD and the cleanup.

there are better descriptions but i am not going to spoon feed you. (any more)
you need to be able to find what is already stickied / a FAQ or in the tutorials, and otherwise well documented, on your own.
DriverPacks has always had a low tolerance for noob like behavior

I have already given you the answer (you need to use the finisher to succeed with the DriverPacks) 
If you continue to chose not to believe me then I can't, and won't try, to help you...
the finisher is how we fix many of the reported issues we get. without it many drivers will not install properly.

and now that you have forced me to explain YET AGAIN what the finisher does... Now I'm annoyed.

All I ask is that you test SAD and post your logs. We'd still like to know how and why it's taking a very long time for the finisher on your your systems. And if it's happening to you perhaps it's also happening to others. And perhaps those others don't behold the same ingenuity of developing their owns scripts so they give up.

By doing so you could possibly not only help yourself but help many others by posting your findings. We'd certainly value that input!

Besides DPinst.exe isn't supported by us, incidentally it's not even supported by Microsoft the developers. So while we use DPinst.exe to install drivers we don't support your use of it.

here is noting should get u annoyed.

i search the site before even started using the base
to get info about the finisher but failed to get find something

at the last i will tell you that
THE SAD IS BAD
close thread PLS ,i realized that i am going right
i do have a copy of this thread to put in the eyes who says
to me you can't do sometihg
Special thanks to whom invent the Base project.

Finisher is required (please search the forum)
I am not going to explain this again here in this thread...
it has been explained 1000 times...
several hundred by me... use search.

select DriverPacks during install is already done and has a GUI...
http://forum.driverpacks.net/viewtopic.php?id=2936
- I am really starting to get annoyed that you will not use the search feature of our forum.
- I am one step away from closing this thread...
start reading the existing material that is already posted here or i will close this thread.

SAD m2 only uses 350 meg for the main packs... not 2 gig or even 600 meg...

add these two lines in presetup.cmd and your done...

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:%TAGFILE%" SET CDDRIVE=%%i:& GOTO DPsFound
:DPsFound

 COPY /Y %CDDRIVE%\OEM\*.* %SystemDrive%\OEM\
 SET CDDRIVE=%SystemDrive%

you don't need to make it any harder than that...
KISS method (Keep It Simple Stupid method)
If you insist on renaming the folder, you can do that from guirunonce or runonceex (before or after the finisher)

optionally include the - "[Add-on] Select desired DriverPacks during M2 install or after install" - I linked to above

You must be running this on a 386 machine if it is taking an hour...
it takes about 10 min for me (with all the main packs) on a slow P4 with an IDE HDD. (no KTD)
If it is taking an hour you have horribly screwed something up...

Yes you're right I can see that SAD is NOT the same as your tool.
- SAD is much better, and so is the pack selection GUI.

Perhaps you should try that AND using the search feature before you post again.

PS I am not a Kid as you refered to me above...
I have been involved with computers since 1968...
My kids are probably older than you are

you said what i've done is the same as SAD which is not indeed
i tell you why
first
i integrate DriverPacks to my CD with M2 i removed KTD this time
(remoing it or keeping it will give no difference for my job)
i need Windows Setup install devices at T35 like sound & graphics & so on
this will saves more time
at the stage where Runonceex entries runs to install applications i used this code to remove %systemDrive%\D & all related files
to safe space that happen at early stage of GUI mode by your presetup.cmd 
**********************
RD /S /Q %systemdrive%\D
%systemdrive%
For %%a in (*.xls *.ini *.exe *.txt *.ins) do del %systemdrive%\"%%a"
************************
instead of using more than 2Gb for DriverPacks i used only 670MB
by making new folder %systemDrive%\Ali\Dpa & copy all compressed packages inside so as to save space as i told before
by running this code
**************
f not Exist %systemDrive%\Ali md %systemDrive%\Ali
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:%TAGFILE%" SET CDDRIVE=%%i:& GOTO DPsFound
:DPsFound
md Ali\DriverPacks
copy /y %CDDRIVE%\OEM\DP*.7z %systemDrive%\Ali\DriverPacks
*************************
i clear Device Path entry value in the registry that you make early by running your DEVPATH.EXE
************
SET KEY=HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion
reg delete %KEY% /V DevicePath /f
reg add %KEY% /V DevicePath /t REG_EXPAND_SZ /D %systemRoot%\inf /f
set KEY=
*************************
by executing the DriverInstaller CMD then i give a menu to the user to select his appropriate package No
from %systemDrive%\Ali\DriverPacks
************
@echo off
Mode Con: Lines=90 Cols=90
color 1f
echo off
for  /f "tokens=1,* delims==" %%a in ('type Re') do echo %%b
set /P NUMB=Select suitable Package No^>
******************
so only the selected package will be exrtacted then
initiating the DPInst.exe to search only the extracted one to save more time than SAD does
Second
the  Ms  DPInst.exe tool u provide is not localized so i downloaded the
localized one for my ararbic users so they know what the wizard instruct them to do
i think According MS White paper after you install ur HD by using this tool noting else is needed
so i wonder why u insist on using finisher afterwards
*****************
to be more clear for my job this my CMD file instead of using DP_Inst_Tool.cmd that will loss our time
& people will hate waiting about an hour to install
just one device
**********************
My CMD file i call it DriverInstaller.cmd

@echo off
Mode Con: Lines=90 Cols=90
color 1f
echo off
for  /f "tokens=1,* delims==" %%a in ('type Re') do echo %%b
set /P NUMB=Select suitable Package No^>

for  /f "tokens=1,2,3 delims== " %%a in ('type Re') do if %NUMB%==%%c set SS=%%a
 
color 4f
un7zip.exe "%systemDrive%\Ali\DriverPacks\%SS%" "%~dp0"

DPInst.exe
RD /S /Q D
For %%a in (*.xls *.ini *.txt *.ins) do del "%%a"
exit
**************************************
after the device get installed
all extracted stuff will be removed to save space
again
**********
you see now that SAD is not the same my job

you must not use the KTD function as this is what takes forever...

I did not release the KTD function... that was done before i was here...

I wrote SAD and it is the replacement for KTD ..

in order for you to get what you were trying to do,
just copy the OEM folder to the HDD... simple...
then run DP_Inst_Tool.cmd when you add new hardware....
does the same thing you were trying to do
and it uses the finisher, which is critical to installing many drivers successfully

Yes i belive you have hit on something that must be done
I am REALLY tired of wasting my breath telling people not to use KTD
I should jsut eliminate it.
That would certainly solve the problem for all the people who refuse to read the many posts about it in the forums.

Normaly i am reluctant to remove existing features from base but...
in this case i am running out of patience arguing the point with people who don't even know what the finisher does.

and Yes I/We do not have time to troubleshoot / evaluate code that duplicates what we already provide...
I doubt i would even have the time if it was something we did not already provide.

I was put off by the fact that someone who does not help us wants us to help them...
You want help from us then you need to help us. 
When a user posts an issue about DriverPacks that helps everyone.

When you just stop by and say
"hey guys I did my own version of what you do and it is not complete will you look at it."
it's not complete because it doesn't use the finisher
I assume he did not use the finisher because he does not understand it.
his problem was the KTD not the finisher...
yet he was unable to arrive at that answer on his own...

He created a problem by useing KTD which we have been saying for years is a dead feature and was replaced by SAD.
He Should have asked for help before he started... not after he invested a bunch of time in duplicating existing work.
this indicates to me he does not do good research before or during going off an a tangent. this strains my patience.
Hey if you want to do somthing as a learning tool fine... but we don't need or want to evaluate it.
that is why i tried to keep my answer short...
I did not want to seem terse, which is something I do fall into easily without meaning to.

His post would have been better recieved had he asked for help first, before he spent days of his time reinventing the wheel.

He said his initial problem was the finisher took so long to complete...
that issue he created himself by enableing KTD... had he simply disabled KTD his problem would have been solved