[ Closed ] Using DPInst.exe Tool

***but thanks for playing***

thank you for ur reply
you are not the only kid how who play with Microsoft stuff
SDK WDK DDK are already with me

no... I meant no offense.  the thanks for playing was a genuine thank you.

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

DP BartPE Tutorial   DP_BASE Tutorial   HWID's Tool     Read BEFORE you post    UserBars!

The DriverPacks, the DP_Base program, and Support Forum are FREE!.

@OverFlow thank u for spending ur time to look around my scribbles
do not worry, the offense cuased by jsut talk
will be suppressed by another talk
i think the aim of my post is to get help from experts
but the title i had put was wrong i think due to the rare
of participating in forums
if you think that selecting KTD is the trouble for the public
i wonder why u give it as an option then
**************************************
i try to pick two birds by one rock
i need the hardware devices be installed during installation
and after but i shoud do it manually
with out using DPsFnshr.exe
this is the goal of my playing

Last edited by FarajAli (2009-04-04 03:45:36)

Mr OverFlow iam very thankfull
this what iam looking for (the help from you)
What is the real job for the finisher
i tried to decompile it but failed
i think it was compressed with Armadillon

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

Last edited by FarajAli (2009-04-04 22:50:05)

see the Mr.OverFlow if u like to close thread
just do it, i am not going to be frustrated
i know that every human likes to be the big boss
& when he did someting thinks that the others can  do noting & thinks
he knows what the paradise looks like
see if you want us to clap the hands for ur project we
do, but we won't allow u to diminish what we are doing

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.

Last edited by FarajAli (2009-04-05 21:49:53)

@kickarse
I don't like to waste ur time but
i like to tell that i don't  want u or anybody else to support my
scripts
because i testd it & worked for me very well
the only thing that iam asking is to know a little summary
about the finisher's job
i thank u for ur polite response
i hoped to know why Microsoft developers don't  support using
DPinst.exe
but no need now to know that
thanks

Last edited by FarajAli (2009-04-06 20:16:14)

That's what i meant to say...     Thanks KA!

----

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.

DP BartPE Tutorial   DP_BASE Tutorial   HWID's Tool     Read BEFORE you post    UserBars!

The DriverPacks, the DP_Base program, and Support Forum are FREE!.

We appreciate your sleuthing. If you could do at least one test with just our full process without any external scripts that would be most helpful. Because it's quite possible that a script that's been written to "help" is what's causing the issue and not SAD.

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

Last edited by stamandster (2009-04-08 00:50:14)